➜

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 Arfrever, pitrou, r.david.murray, rogerbinns, serhiy.storchaka, skrah, vstinner
Date 2012-10-05.22:30:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349476257.47.0.441080710161.issue16145@psf.upfronthosting.co.za>
In-reply-to
Content 
"In general APSW does not look ready for the Python 3.3 Unicode implementation."

I bet that most Python modules implemented in C use the "legacy" (old) Unicode API (Py_UNICODE*). Python 3.3 must call PyUnicode_READY() everywhere (where the new API is used to get attribute of a string, ex: PyUnicode_GET_LENGTH).
History
Date User Action Args
2012-10-05 22:30:57vstinnersetrecipients: + vstinner, pitrou, rogerbinns, Arfrever, r.david.murray, skrah, serhiy.storchaka
2012-10-05 22:30:57vstinnersetmessageid: <1349476257.47.0.441080710161.issue16145@psf.upfronthosting.co.za>
2012-10-05 22:30:57vstinnerlinkissue16145 messages
2012-10-05 22:30:57vstinnercreate