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 r.david.murray
Recipients Gumnos, amaury.forgeotdarc, eric.araujo, meatballhat, r.david.murray
Date 2010-05-10.19:25:59
SpamBayes Score 0.000554059
Marked as misclassified No
Message-id <1273519561.51.0.527977903614.issue8666@psf.upfronthosting.co.za>
In-reply-to
Content
Rather than a raise_on_bad option, it seems to me it would be better to code a try/except clause in cases where you want the default even if there is an error converting the data in the file.  I would expect such cases to be rare, except for cases where you want to issue a warning message and then proceed with the default anyway, in which case you'd need the try/except anyway in order to issue the warning message.
History
Date User Action Args
2010-05-10 19:26:01r.david.murraysetrecipients: + r.david.murray, amaury.forgeotdarc, eric.araujo, meatballhat, Gumnos
2010-05-10 19:26:01r.david.murraysetmessageid: <1273519561.51.0.527977903614.issue8666@psf.upfronthosting.co.za>
2010-05-10 19:26:00r.david.murraylinkissue8666 messages
2010-05-10 19:25:59r.david.murraycreate