[issue13212] json library is decoding/encoding when it should not

[Petri Lehtinen]

Petri Lehtinen added the comment:

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.

----------
nosy: +petri.lehtinen

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13212>
_______________________________________