> The resources to pay someone doesn’t mean that someone with interest and knowledge exists That's why you can pay people. So that despite their disinterest th

> The resources to pay someone doesn’t mean that someone with interest and knowledge exists That's why you can pay people. So that despite their disinterest they will read the code and acquire the knowledge needed. > especially for modules that were formally deprecated in Python 2 ??? I'm talking about modules removed now, in 2024. They were not deprecated since python2. Please don't steer the conversation to different topics. > Lots of this stuff is just cruft, most of which has an obvious replacement distutils? Is it cruft? The thing used to install modules? Can you tell me which stdlib replacement it has? > it’s not been used in years by anyone Why did I have to patch over 10 modules? > and if it ever had a reason to be in the standard lib, that reason is long gone Is installing modules no longer a thing then? > those distro maintainers are harming everyone. Aaah yes, the evil distro maintainers that keep things working instead of breaking everything. They're the real culprits here… really? > I’ve written plenty of Python scripts that are still running on the interpreter and stdlib they were authored for, decades later. Decades later? That's at least 20 years. If that were true they'd be written in python2 and I can promise you they wouldn't work with python 3.12. So I'll consider this statement a lie. Please try to be more honest when you interact with me the next time. This hasn't been pleasant.