3 ms·
I feel that every release, the python team should do some soul searching and pick 5 modules to downgrade to external package(pypi) status, then pick 5 deserving
by somat 5y ago
I feel that every release, the python team should do some soul searching and pick 5 modules to downgrade to external package(pypi) status, then pick 5 deserving external packages and elevate them to base status.
This would, for one, add a bit of churn to the standard library leading to a more healthy ecosystem. And two, give everyone a target to complain about, I mean, people are going to complain about something, might as well focus their attention.
- jphoward 5y agoBecause dependency hell isn't dreadful enough? Some entries will be completely missing from requirements.txt because the person assumes a certain version of python is present.
- overgard 5y agoThat would make upgrading the interpreter version terrifying
- MengerSponge 5y agoFurthermore, imagine the joy of a package winning the Premier League just a year after returning from relegation?
- selfhoster11 5y agoThat would result in a mini-Python 2/3 catastrophe every release. No, thank you. Maybe that's acceptable when you're the author of a piece of software, but as an ops engineer, that prospect makes my hair stand on end.
- oblvious-earth 5y agoVery few modules in the standard library actually get deprecated, that's why this PEP got put together. It also took 3 years of discussion to achieve consensus and the initial list was whittled down quite a bit and the reasoning became much stronger on the final list. And these aren't even being removed until Python 3.13! The SC have also said this is a one time event and they won't accept a similar PEP in the future, modules in the future most be handled on a case by case basis and the preferred outcome will not be to remove them.