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 rhettinger
Recipients belopolsky, johnwalker, mark.dickinson, python-dev, rhettinger, serhiy.storchaka, skrah, steven.daprano, terry.reedy, tim.peters
Date 2016-04-05.02:39:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I don't think a new public method should have been added.

Historically, we've been careful to not grow the API beyond what is in the spec or the dunder methods required to interface with standard Python.

The feature creep is at odds with the intended goals for the module that have been present since the outset.  As long as the spec remains unchanged, the API for this module should be treated as stable.

Another issue is that the API for the module is already so large that it impairs usability.  Please don't make it worse by adding new methods and inventing details that aren't in the spec.
Date User Action Args
2016-04-05 02:39:13rhettingersetrecipients: + rhettinger, tim.peters, terry.reedy, mark.dickinson, belopolsky, steven.daprano, skrah, python-dev, serhiy.storchaka, johnwalker
2016-04-05 02:39:13rhettingersetmessageid: <>
2016-04-05 02:39:13rhettingerlinkissue25928 messages
2016-04-05 02:39:12rhettingercreate