➜

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 thomaslee
Recipients alexey-smirnov, cvrebert, ezio.melotti, pitrou, socketpair, thomaslee
Date 2012-09-28.06:59:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348815595.44.0.174135728914.issue14886@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2012-09-28 06:59:55thomasleesetrecipients: + thomaslee, pitrou, ezio.melotti, cvrebert, socketpair, alexey-smirnov
2012-09-28 06:59:55thomasleesetmessageid: <1348815595.44.0.174135728914.issue14886@psf.upfronthosting.co.za>
2012-09-28 06:59:54thomasleelinkissue14886 messages
2012-09-28 06:59:54thomasleecreate