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 josh.r
Recipients josh.r, wbolster
Date 2015-02-21.00:43:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Is it even legal to have non-string keys in a JSON object? If they must be strings, and they must be unique, I don't think a key argument is necessary (and it would save the generation of the key array; not doing the work is faster than doing the work more efficiently after all), since the default tuple comparison would work fine; the first element would always be unequal, so the second elements would never be compared, right?

I'm not 100% on this with the rich comparison operator approach, but my attempts to trigger a failure haven't worked (TimSort or the tuple comparison, or both, are probably smarter about this than I am).
Date User Action Args
2015-02-21 00:43:21josh.rsetrecipients: + josh.r, wbolster
2015-02-21 00:43:21josh.rsetmessageid: <>
2015-02-21 00:43:21josh.rlinkissue23493 messages
2015-02-21 00:43:21josh.rcreate