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 petri.lehtinen
Recipients ghaering, petri.lehtinen, pitrou
Date 2012-02-02.16:11:56
SpamBayes Score 1.4237609e-05
Marked as misclassified No
Message-id <1328199117.02.0.5298614101.issue13921@psf.upfronthosting.co.za>
In-reply-to
Content
Attached a patch. It changes OptimizedUnicode to be an alias for PyUnicode_Type and adds a note to the documentation for porters from 2.x that it has no effect on py3k.

The patch removes/refactors all OptimizedUnicode and allow_8bit_chars related obsolete code that had been left over from py3k transition. These removals/refactorizations have no operational effect, so the module still works the same way it has always worked in Py3k.

Should OptimizedUnicode be deprecated, too? In this case, it cannot be aliased to str, and _pysqlite_fetch_one_row() needs to raise a DeprecationWarning if OptimizedUnicode is used.
History
Date User Action Args
2012-02-02 16:11:57petri.lehtinensetrecipients: + petri.lehtinen, ghaering, pitrou
2012-02-02 16:11:57petri.lehtinensetmessageid: <1328199117.02.0.5298614101.issue13921@psf.upfronthosting.co.za>
2012-02-02 16:11:56petri.lehtinenlinkissue13921 messages
2012-02-02 16:11:56petri.lehtinencreate