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 docs@python, ezio.melotti, marco.buttu, r.david.murray
Date 2012-10-29.16:07:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351526859.88.0.50258758666.issue16355@psf.upfronthosting.co.za>
In-reply-to
Content
> After I thought about it some more I realized that changing
> the behavior to raise an error would not be a good idea.

Can you elaborate more?
Failing silently doesn't seem much better than raising an error, especially if similar functions already raise.
History
Date User Action Args
2012-10-29 16:07:39ezio.melottisetrecipients: + ezio.melotti, r.david.murray, docs@python, marco.buttu
2012-10-29 16:07:39ezio.melottisetmessageid: <1351526859.88.0.50258758666.issue16355@psf.upfronthosting.co.za>
2012-10-29 16:07:39ezio.melottilinkissue16355 messages
2012-10-29 16:07:39ezio.melotticreate