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 ezio.melotti
Recipients Charlie.Dimino, docs@python, ezio.melotti, r.david.murray, tshepang
Date 2013-01-04.17:24:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357320260.25.0.928312856504.issue16863@psf.upfronthosting.co.za>
In-reply-to
Content
When I backported the patch I probably didn't want to try all the examples to see what the py2 error was.  In addition the py3 error is more clear even if it doesn't match what you actually get.
I think this can be closed as won't fix, unless someone wants to propose a patch.
History
Date User Action Args
2013-01-04 17:24:20ezio.melottisetrecipients: + ezio.melotti, r.david.murray, docs@python, tshepang, Charlie.Dimino
2013-01-04 17:24:20ezio.melottisetmessageid: <1357320260.25.0.928312856504.issue16863@psf.upfronthosting.co.za>
2013-01-04 17:24:20ezio.melottilinkissue16863 messages
2013-01-04 17:24:20ezio.melotticreate