➜

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 pitrou
Recipients dholth, pitrou, r.david.murray, serhiy.storchaka, vstinner
Date 2013-07-18.08:21:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1374135660.44.0.941678151006.issue18373@psf.upfronthosting.co.za>
In-reply-to
Content 
> if
> (perhaps someone is calling your library and passing it the wrong type)
> they would be guarded against this common error.

OTOH, if your library is concerned about unwanted bytes objects, you can add an explicit type check.
That said, I don't see any counter-argument against this proposal; only that I'm not sure it's very useful.
History
Date User Action Args
2013-07-18 08:21:00pitrousetrecipients: + pitrou, vstinner, r.david.murray, dholth, serhiy.storchaka
2013-07-18 08:21:00pitrousetmessageid: <1374135660.44.0.941678151006.issue18373@psf.upfronthosting.co.za>
2013-07-18 08:21:00pitroulinkissue18373 messages
2013-07-18 08:21:00pitroucreate