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 nnorwitz
Recipients
Date 2006-08-13.00:02:27
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=33168

I don't know the intricasies of rich comparisons, but this
looks pretty good.  There are some typos: silcence (drop the
first c, comment in unicodeobject.c).  I think the doc
(Doc/lib/libexcs.tex) is missing an \end{excdesc}.  In
Misc/NEWS, "can be then filtered" is awkward, drop the
'then'.  Misc/NEWS should mention the new public API
PyUnicode_RichCompare (and point out that UnicodeWarning is
new).

Please check this in ASAP and report to python-dev.  That
way if there are any issues, we can try to resolve them
quickly.  People are more likely to review the checkin the
patch on SF.

Improving warnings in 2.6 would definitely be nice.
History
Date User Action Args
2007-08-23 15:54:05adminlinkissue1538956 messages
2007-08-23 15:54:05admincreate