Remove formatter module from Python 3.9, deprecated for 7 years (Python 3.4)
Hi, I proposed https://bugs.python.org/issue39352 to remove the formatter module. It's deprecated since Python 3.4. The main reason why it's still around is the PEP 4 rule: "In order to facilitate writing code that works in both Python 2 & 3 simultaneously, any module that exists in both Python 3.5 and Python 2.7 will not be removed from the standard library until Python 2.7 is no longer supported as specified by PEP 373." https://www.python.org/dev/peps/pep-0004/#for-modules-existing-in-both-pytho... Python 2.7 is not longer supported. So can we now remove the formatter module? The module has no test, I failed to find any user in a dummy GitHub code search and I didn't know that this module even existed. We can still revert the module before 3.9.0 final release if someone shows up and asks to keep it for one more cycle. My intent here is to reduce the size of the Python standard library to reduce the maintenance burden. Python became quite large and it's more and more expensive to maintain it. Wait... I'm not asking to remove all modules of the standard library :-) The decision must be taken on a case by case basis, for each module. Here I'm only taking about the formatter module. Victor -- Night gathers, and now my watch begins. It shall not end until my death.
I have no objections, the module raises the explicit deprecation warning since 2013. On Fri, Jan 17, 2020 at 7:31 PM Victor Stinner <vstinner@python.org> wrote:
Hi,
I proposed https://bugs.python.org/issue39352 to remove the formatter module. It's deprecated since Python 3.4. The main reason why it's still around is the PEP 4 rule:
"In order to facilitate writing code that works in both Python 2 & 3 simultaneously, any module that exists in both Python 3.5 and Python 2.7 will not be removed from the standard library until Python 2.7 is no longer supported as specified by PEP 373."
https://www.python.org/dev/peps/pep-0004/#for-modules-existing-in-both-pytho...
Python 2.7 is not longer supported. So can we now remove the formatter module?
The module has no test, I failed to find any user in a dummy GitHub code search and I didn't know that this module even existed.
We can still revert the module before 3.9.0 final release if someone shows up and asks to keep it for one more cycle.
My intent here is to reduce the size of the Python standard library to reduce the maintenance burden. Python became quite large and it's more and more expensive to maintain it. Wait... I'm not asking to remove all modules of the standard library :-) The decision must be taken on a case by case basis, for each module. Here I'm only taking about the formatter module.
Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/ESSRZXEJ... Code of Conduct: http://python.org/psf/codeofconduct/
-- Thanks, Andrew Svetlov
+1 remove it to match that policy. I find it unlikely someone will ask for it to be restored, but our first response before doing so should be to see if they can instead use it as a dependency via PyPI: Someone who wants to maintain it for future use can take 3.8 formatter module and put it there. -gps On Fri, Jan 17, 2020 at 10:43 AM Andrew Svetlov <andrew.svetlov@gmail.com> wrote:
I have no objections, the module raises the explicit deprecation warning since 2013.
On Fri, Jan 17, 2020 at 7:31 PM Victor Stinner <vstinner@python.org> wrote:
Hi,
I proposed https://bugs.python.org/issue39352 to remove the formatter module. It's deprecated since Python 3.4. The main reason why it's still around is the PEP 4 rule:
"In order to facilitate writing code that works in both Python 2 & 3 simultaneously, any module that exists in both Python 3.5 and Python 2.7 will not be removed from the standard library until Python 2.7 is no longer supported as specified by PEP 373."
https://www.python.org/dev/peps/pep-0004/#for-modules-existing-in-both-pytho...
Python 2.7 is not longer supported. So can we now remove the formatter
module?
The module has no test, I failed to find any user in a dummy GitHub code search and I didn't know that this module even existed.
We can still revert the module before 3.9.0 final release if someone shows up and asks to keep it for one more cycle.
My intent here is to reduce the size of the Python standard library to reduce the maintenance burden. Python became quite large and it's more and more expensive to maintain it. Wait... I'm not asking to remove all modules of the standard library :-) The decision must be taken on a case by case basis, for each module. Here I'm only taking about the formatter module.
Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/ESSRZXEJ...
Code of Conduct: http://python.org/psf/codeofconduct/
-- Thanks, Andrew Svetlov _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/BHCWXBTE... Code of Conduct: http://python.org/psf/codeofconduct/
As another datapoint, in an internal codebase with a high XX million lines of Python code, I see a mere 7 uses. Most of which are in legacy things that would be trivial to use f-strings instead if the code doesn't just get deleted when the owners notice. :) (and my team is responsible for upgrading us to 3.9 so we'd simply make that happen at that time) -gps On Fri, Jan 17, 2020 at 11:09 AM Gregory P. Smith <greg@krypto.org> wrote:
+1 remove it to match that policy. I find it unlikely someone will ask for it to be restored, but our first response before doing so should be to see if they can instead use it as a dependency via PyPI: Someone who wants to maintain it for future use can take 3.8 formatter module and put it there.
-gps
On Fri, Jan 17, 2020 at 10:43 AM Andrew Svetlov <andrew.svetlov@gmail.com> wrote:
I have no objections, the module raises the explicit deprecation warning since 2013.
On Fri, Jan 17, 2020 at 7:31 PM Victor Stinner <vstinner@python.org> wrote:
Hi,
I proposed https://bugs.python.org/issue39352 to remove the formatter module. It's deprecated since Python 3.4. The main reason why it's still around is the PEP 4 rule:
"In order to facilitate writing code that works in both Python 2 & 3 simultaneously, any module that exists in both Python 3.5 and Python 2.7 will not be removed from the standard library until Python 2.7 is no longer supported as specified by PEP 373."
https://www.python.org/dev/peps/pep-0004/#for-modules-existing-in-both-pytho...
Python 2.7 is not longer supported. So can we now remove the formatter
module?
The module has no test, I failed to find any user in a dummy GitHub code search and I didn't know that this module even existed.
We can still revert the module before 3.9.0 final release if someone shows up and asks to keep it for one more cycle.
My intent here is to reduce the size of the Python standard library to reduce the maintenance burden. Python became quite large and it's more and more expensive to maintain it. Wait... I'm not asking to remove all modules of the standard library :-) The decision must be taken on a case by case basis, for each module. Here I'm only taking about the formatter module.
Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/ESSRZXEJ...
Code of Conduct: http://python.org/psf/codeofconduct/
-- Thanks, Andrew Svetlov _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/BHCWXBTE... Code of Conduct: http://python.org/psf/codeofconduct/
participants (3)
-
Andrew Svetlov -
Gregory P. Smith -
Victor Stinner