Message168960
| Author |
petri.lehtinen |
| Recipients |
eric.araujo, ezio.melotti, flox, petri.lehtinen, pitrou, rhettinger, thinred, vstinner |
| Date |
2012年08月23日.19:20:20 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1345749620.92.0.848953090427.issue13212@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The strict flag sounds good to me, too. 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()). How about "encode_any" and "decode_any" or "any_value"?
Deprecation doesn't sound good to me. If the feature is already there, it probably has its users and use cases. |
|