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 bob.ippolito
Recipients Arfrever, bob.ippolito, ezio.melotti, pitrou, r.david.murray, rhettinger, serhiy.storchaka
Date 2013-09-01.23:10:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378077055.75.0.229497923438.issue18726@psf.upfronthosting.co.za>
In-reply-to
Content
I tend to agree with Raymond here. While I also don't like the positional arguments, I don't think the benefit of API churn them is high enough to remove them. Other than this issue, I have not seen any requests for this change.

I have seen problems because there are positional arguments, but only when people are subclassing these classes. Allowing for subclasses was never a good idea, and is actively discouraged in current simplejson documentation. The dumps default/loads object_hook functionality is sufficient and doesn't have the fragile base class problem. This functionality is is fully compatible with all versions of the library that are in use, back to v1.8 in March 2008, including Python 2.6's json library which IIRC is based on v1.9.
History
Date User Action Args
2013-09-01 23:10:55bob.ippolitosetrecipients: + bob.ippolito, rhettinger, pitrou, ezio.melotti, Arfrever, r.david.murray, serhiy.storchaka
2013-09-01 23:10:55bob.ippolitosetmessageid: <1378077055.75.0.229497923438.issue18726@psf.upfronthosting.co.za>
2013-09-01 23:10:55bob.ippolitolinkissue18726 messages
2013-09-01 23:10:55bob.ippolitocreate