Author gruszczy
Recipients dangyogi, flox, gruszczy
Date 2010-03-28.22:59:10
SpamBayes Score 2.13491e-07
Marked as misclassified No
Message-id <1269817152.03.0.0757620123292.issue8256@psf.upfronthosting.co.za>
In-reply-to
Content
The bug is triggered by input, not by print. The exact place is _PyUnicode_AsStringAndSize, where unicode check happens. Then print checks PyError_Occured and catches this error. Either this error should not be raised or should be cleared input finishes.

I'd love to provide a patch, but I have no idea, what should be corrected and how. If some would tutor me a little, I would be very happy to learn and code this.
History
Date User Action Args
2010-03-28 22:59:12gruszczysetrecipients: + gruszczy, dangyogi, flox
2010-03-28 22:59:12gruszczysetmessageid: <1269817152.03.0.0757620123292.issue8256@psf.upfronthosting.co.za>
2010-03-28 22:59:10gruszczylinkissue8256 messages
2010-03-28 22:59:10gruszczycreate