[issue2512] decide what to do with gettext API

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: done in r64947. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2512] decide what to do with gettext API

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is something that should definitely happen before beta 2. -- priority: critical -> release blocker ___ Python tracker <[EMAIL PROTECTED]>

[issue2512] decide what to do with gettext API

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I've pushed a fresh branch and am attaching a new patch. Added file: http://bugs.python.org/file10153/gettext_api2.patch __ Tracker <[EMAIL PROTECTED]> ___

[issue2512] decide what to do with gettext API

Guido van Rossum <[EMAIL PROTECTED]> added the comment: This patch doesn't apply cleanly. :-( -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2512] decide what to do with gettext API

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file9896/gettext_api.patch __ Tracker <[EMAIL PROTECTED]> __ ___ Py

[issue2512] decide what to do with gettext API

New submission from Benjamin Peterson <[EMAIL PROTECTED]>: The gettext module currently has functions and methods beginning with "u" to designate functions which return unicode objects. The install function/method also has a "unicode" parameter. These are obviously useless in Py3k. The attached p