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 PythonInTheGrass
Recipients PythonInTheGrass, pitrou, terry.reedy
Date 2011-01-22.13:25:28
SpamBayes Score 1.5896237e-06
Marked as misclassified No
Message-id <000001cbba37$d03ae780$70b0b680$@mayo@comcast.net>
In-reply-to <1295667797.82.0.939393478038.issue10909@psf.upfronthosting.co.za>
Content
Moving to 3.x means redoing large swaths of the extension I just wrote. It's only a couple thousand lines, but it was my first extension and it cost me a week of my life in Google, and it does a lot with strings.

I haven't pulled down the source code for Python's internals yet, but from the one trace back I did get in the failing thread test app, the problem was inside print and it looked like it was inside the mechanism where print gets redirected. I hope the problem isn't anything as fundamental as the GIL, because that throws the stability of all of 2.7 into question (and it's been solid in all my tests; I do a lot with threads in my extension, all going after the GIL and diving into Python code.)
History
Date User Action Args
2011-01-22 13:25:32PythonInTheGrasssetrecipients: + PythonInTheGrass, terry.reedy, pitrou
2011-01-22 13:25:28PythonInTheGrasslinkissue10909 messages
2011-01-22 13:25:28PythonInTheGrasscreate