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 lemburg
Recipients amaury.forgeotdarc, lemburg, serhiy.storchaka
Date 2013-05-15.07:34:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368603268.32.0.160337067017.issue17979@psf.upfronthosting.co.za>
In-reply-to
Content
Please note that the official way to build Python without Unicode 
support is (see http://bugs.python.org/issue445762):

./configure --disable-unicode

See http://bugs.python.org/issue8767 for the most recent set of fixes 
that were supplied to make it work again in Python 2.7.4.

If the above doesn't work, it's a bug (as well) - and has been for
quite a few releases. Technically, --disable-unicode is mapped to 
--enable-unicode=no by configure.

I guess we'd need a buildbot to check whether --disable-unicode still
works, i.e. produces a Python version that compiles and passes
the basic tests.
History
Date User Action Args
2013-05-15 07:34:28lemburgsetrecipients: + lemburg, amaury.forgeotdarc, serhiy.storchaka
2013-05-15 07:34:28lemburgsetmessageid: <1368603268.32.0.160337067017.issue17979@psf.upfronthosting.co.za>
2013-05-15 07:34:28lemburglinkissue17979 messages
2013-05-15 07:34:28lemburgcreate