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 eric.smith
Recipients eric.smith, oz.tamir
Date 2015-05-28.14:16:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432822576.83.0.115963354557.issue24312@psf.upfronthosting.co.za>
In-reply-to
Content
As a rule, we don't put in checks like this. There are an untold number of places where such checks could be added. I suspect the new typing module will be a better way to catch these types of errors.

Does the problem not occur with 3.5?
History
Date User Action Args
2015-05-28 14:16:16eric.smithsetrecipients: + eric.smith, oz.tamir
2015-05-28 14:16:16eric.smithsetmessageid: <1432822576.83.0.115963354557.issue24312@psf.upfronthosting.co.za>
2015-05-28 14:16:16eric.smithlinkissue24312 messages
2015-05-28 14:16:16eric.smithcreate