Thomas Lee added the comment: FWIW, I think Mark's right here. I'm +1 on the implementations being consistent.
Seems like a potentially nasty surprise if you move from one implementation to the other and, lacking awareness of this quirk, design your algorithm around semantics. I think this was Mark's original point. If the json API doesn't care how the type check is performed, then we get a (probably very small :)) win from the type(o) in (list, tuple) for the Python impl in addition to bringing consistency to the two implementations. ---------- nosy: +thomaslee _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14886> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
