Message221438
| Author |
vstinner |
| Recipients |
benjamin.peterson, ezio.melotti, loewis, michael.foord, ned.deily, pitrou, serhiy.storchaka, skrah, vstinner |
| Date |
2014年06月24日.08:50:39 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1403599839.92.0.526278418219.issue21833@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
IMO supporting building Python 2 without Unicode support should be discussed on the python-dev mailing list, it's not an innocent change.
Python is moving strongly to Unicode: Python 3 uses Unicode by default. So to me it sounds really weird to work on building Python 2 without Unicode support. It means that you may have "Python 2" and "Python 2 without Unicode" which are not exactly the same language. IMO u"unicode" is part of the Python 2 language.
--disable-unicode is an old option added while Python 1.5 was very slowly moving to Unicode.
--
I have the same opinion on --without-thread option (we should stop supporting it, this option is useless). I worked in the embedded world, Python used for the UI of a TV set top box. Even if the hardware was slow and old, Python was compiled with threads and Unicode. Unicode was mandatory to handle correctly letters with diacritics. |
|