On 04Jun2019 1721, Victor Stinner wrote:
So what is happening for this PEP since Python 3.8 beta1 has been
released? Is it too late for Python 3.8 or not?
It seems like most people are confused by the intent of the PEP. IMHO
it would be better to rewrite "Remove packages from the stdlib" as
"Move some stdlib modules to PyPI". But that would require to rewrite
some parts of the PEP to explain how modules are moved, who become the
new maintainers, how to support modules both in stdlib (old Python
versions) and in PyPI (new Python), etc.
I think the problem with this is it sounds like the longer-term plan to
maintain some stdlib packages independently of the CPython repo, *but
still include them in the distro* (ensurepip style). This is a much
broader set of packages that would still be available by default
(assuming that distributors care about their users) but would also
benefit from a single code base (rather than 3-4 branches) and being
independently upgradeable (for backports and/or security fixes). They
would probably still be managed by core developers, and it may be easier
to attract new contributors for them since they don't need to manage the
entire CPython repo.
By contrast, the packages in this PEP are just being deprecated and
removed. We don't actually have to explain what happens next, and we
don't have to block the PEP on those discussions.
But perhaps we should go for the big refactor now? Then at least we have
an explanation for unmaintained packages too - they still show up in
distros but are not part of the CPython source tree.
Cheers,
Steve
Python-Dev mailing list -- python-dev(a)python.org
To unsubscribe send an email to python-dev-leave(a)python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
