Ezio Melotti <ezio.melo...@gmail.com> added the comment: > You're right: my wide build is not Python3, just Python2.
And is it failing? Here the tests pass on the wide builds, on both Python 2 and 3. > In fact, it's even worse, because it's the stock build on Linux, > which seems on this machine to be 2.6 not 2.7. What is worse? FWIW on my system the default `python` is a 2.7 wide. `python3` is a 3.2 wide. > I have private builds that are 2.7 and 3.2, but those are both narrow. > I do not have a 3.3 build. Should I? 3.3 is the version in development, not released yet. If you have an HG clone of Python you can make a wide build of 3.x with ./configure --with-wide-unicode andof 2.7 using ./configure --enable-unicode=ucs4. > I'm remembering why I removed Python2 from my Unicode talk, because > of how it made me pull my hair out. People at the talk wanted to know > what I meant, but I didn't have time to go into it. I think this > gets added to the hairpulling list. I'm not sure what you are referring to here. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12749> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
