Perhaps if PEP 594 is seen to be moving ahead towards a slimmer Python (4?) stdlib, it might encourage the development of a PEP to take over maintenance of dead parrots. They might be recruited by the offer of some way to at least publish a supported bundle via the same (python.org) site that Python itself comes from. It would seem unfair to burden the PEP with promising an afterlife. That would raise quality assurance issues, though.
If no such PEP emerges then the dead parrots will be buried and forgotten. I see little reason why we (Python users) shouldn't trust the collective python-dev wisdom on what ultimately belongs in stdlib, and heaven knows these aren't simple discussions. On Wed, Jun 5, 2019 at 6:56 PM Brett Cannon <br...@python.org> wrote: > > > On Tue, Jun 4, 2019 at 5:22 PM Victor Stinner <vstin...@redhat.com> 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. >> > > Correct, that is more than a title change but a shift in what the PEP's > final result is. And the title as it currently stands as the modules would > still be removed from the stdlib regardless of whether they end up on PyPI > or not. > Python-Dev mailing list -- python-dev(a)python.org > To unsubscribe send an email to python-dev-leave(a)python.org > Unsubscribe: > https://mail.python.org/mailman3/lists/python-dev.python.org/
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/
