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 tchrist
Recipients Arfrever, ezio.melotti, jkloth, mrabarnett, pitrou, r.david.murray, rhettinger, tchrist, terry.reedy
Date 2011-08-14.16:57:16
SpamBayes Score 3.8490838e-10
Marked as misclassified No
Message-id <25204.1313341025@chthon>
In-reply-to <1313338008.86.0.287608821741.issue12749@psf.upfronthosting.co.za>
Content
>Ezio Melotti <ezio.melotti@gmail.com> added the comment:

>On wide 3.2 it passes too, so the failure is limited to narrow builds (are =
>you sure that it fails on wide builds for you?).

You're right: my wide build is not Python3, just Python2.  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.

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?

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.

--tom
History
Date User Action Args
2011-08-14 16:57:17tchristsetrecipients: + tchrist, rhettinger, terry.reedy, pitrou, jkloth, ezio.melotti, mrabarnett, Arfrever, r.david.murray
2011-08-14 16:57:16tchristlinkissue12749 messages
2011-08-14 16:57:16tchristcreate