➜

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 vstinner
Recipients ezio.melotti, lemburg, serhiy.storchaka, vstinner, wiml
Date 2013-04-14.14:28:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365949718.48.0.795493208532.issue15866@psf.upfronthosting.co.za>
In-reply-to
Content 
Should we really invest time to fix bugs related to astral (non-BMP) characters with rare codecs and error handlers (CJK codecs, xmlcharrefreplace error handler)? Python 3.3 is released and has a much better support of astral characters (in many places). I don't know for CJK codecs: Python 3.3 still uses the legacy Unicode API for CJK codecs and so depend on the wchar_t type (which is 16 bits on Windows). I just fixed Python 3.4 to use the new Unicode API (PEP 393), which always support astral characters support and don't depend on the size of the wchar_t type.

I'm not against fixing Python 2.7, I'm just not interested.
History
Date User Action Args
2013-04-14 14:28:38vstinnersetrecipients: + vstinner, lemburg, ezio.melotti, wiml, serhiy.storchaka
2013-04-14 14:28:38vstinnersetmessageid: <1365949718.48.0.795493208532.issue15866@psf.upfronthosting.co.za>
2013-04-14 14:28:38vstinnerlinkissue15866 messages
2013-04-14 14:28:38vstinnercreate