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 Alex Gordon, andrewnester, benhoyt, berker.peksag, bob.ippolito, brett.cannon, r.david.murray, rhettinger, serhiy.storchaka, vstinner
Date 2017-02-19.19:58:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I would recommend a moratorium on new options until we have a plan to make the usage of the JSON APIs simpler overall. It's accumulated too many options over time. The real trouble is figuring out how to do this in a backwards compatible way that does not impact performance too much. Off-hand, I can't think of any obvious way aside from using new function names with a cleaner options list.
Date User Action Args
2017-02-19 19:58:40bob.ippolitosetrecipients: + bob.ippolito, brett.cannon, rhettinger, vstinner, r.david.murray, benhoyt, berker.peksag, serhiy.storchaka, Alex Gordon, andrewnester
2017-02-19 19:58:40bob.ippolitosetmessageid: <>
2017-02-19 19:58:40bob.ippolitolinkissue29540 messages
2017-02-19 19:58:40bob.ippolitocreate