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.araujo
Recipients cvrebert, eric.araujo, ezio.melotti, flox,, petri.lehtinen, pitrou, rhettinger, thinred, vstinner
Date 2012-09-10.14:56:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't think it should be called "strict" though, as that would imply that we comply with RFC 4627 strictly
> (which is not true without passing allow_nan=False for dump() or  passing a parse_constant function for load())

What if the strict mode implied both of these things?

FWIW, I’m +1 for a doc section about how to achieve strict mode with special arguments and callbacks (if the recent doc patch does not already have that), and +0 on adding it to the code itself.
Date User Action Args
2012-09-10 14:56:36eric.araujosetrecipients: + eric.araujo, rhettinger, pitrou, vstinner, ezio.melotti, cvrebert, flox, petri.lehtinen, thinred,
2012-09-10 14:56:36eric.araujosetmessageid: <>
2012-09-10 14:56:35eric.araujolinkissue13212 messages
2012-09-10 14:56:35eric.araujocreate