This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, docs@python, loewis
Date 2010-12-10.18:31:15
SpamBayes Score 4.096126e-08
Marked as misclassified No
Message-id <AANLkTin-ZZpwwp0N5mJzTwZok19WNVpcUwaWyEUVS9BU@mail.gmail.com>
In-reply-to
Content
On Thu, Dec 9, 2010 at 6:10 PM, Martin v. Löwis <report@bugs.python.org> wrote:
..
> Please, one issue per report and checkin,

The s/5.2/6.0/ issue is hardly worth a tracker ticket.   I've
committed these changes in r87159.  (Sorry for the unrelated changes -
reverted in the next checkin.)

> and no work-in-progress on the tracker.

Why?  I thought "release early, release often" was a good thing.   I
wanted to get an early feedback because we certainly don't want to
replicate the Unicode Standard in the Python documentation, but I
think at least for the category() method that returns cryptic 2-letter
codes, we should include a table explaining them.   I am not so sure
about bidirectional() or asian_width().

> The issue of factually correcting claims about the unicodedata module and elaborations on how it works are unrelated issues.

I am changing the title of the issue to make it cover only the latter.
>
> ----------
> nosy: +loewis
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue10665>
> _______________________________________
>
History
Date User Action Args
2010-12-10 18:31:18belopolskysetrecipients: + belopolsky, loewis, docs@python
2010-12-10 18:31:15belopolskylinkissue10665 messages
2010-12-10 18:31:15belopolskycreate