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 petr.viktorin
Recipients aganders3, aviramha, bar.harel, benjamin.peterson, brandtbucher, bukzor, georg.brandl, levkivskyi, methane, miss-islington, petr.viktorin, pitrou, rhettinger, serhiy.storchaka
Date 2022-01-19.13:39:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642599567.73.0.750824723173.issue46376@roundup.psfhosted.org>
In-reply-to
Content
Changing the existing functions is a no-go for backwards compatibility reasons. I think the best way forward would be to add a new function, and then possibly deprecate the old one if it's deemed dangerous.

If you want to push this forward, could you summarize the use case(s) and expected behavior (docs) for such a function? It probably doesn't need a PEP, but it's worth looking here for what to think about when making a proposal: https://www.python.org/dev/peps/pep-0001/#what-belongs-in-a-successful-pep
History
Date User Action Args
2022-01-19 13:39:27petr.viktorinsetrecipients: + petr.viktorin, georg.brandl, rhettinger, pitrou, benjamin.peterson, methane, bukzor, aganders3, serhiy.storchaka, levkivskyi, bar.harel, miss-islington, brandtbucher, aviramha
2022-01-19 13:39:27petr.viktorinsetmessageid: <1642599567.73.0.750824723173.issue46376@roundup.psfhosted.org>
2022-01-19 13:39:27petr.viktorinlinkissue46376 messages
2022-01-19 13:39:27petr.viktorincreate