Perhaps there shouldn’t be constant breaking changes?
Also unpaid contributors move on with their life. If something is fun (like a new feature) they might feel like doing it, but if it feels like work (setting up github runners to publish on pypi and risk getting hacked, do yearly meaningless changes to support the new python) they might decide it’s not worth doing it.
In that case of course the problem is that pypi has no way to transfer ownership of abandoned projects, so they remain there forever unused.
I think that the python project should make things easier and less miserable, instead of blaming unpaid contributors that they aren’t working hard enough.
There is a way (albeit a slow one). You make a PEP 541 request.
FWIW, I would happily sacrifice all the new features that came in after Python 3.6 if it meant that I could have skipped the imp → importlib migration, loaders, metapath finders and all the back and forth around importlib.resources+predecessors.
May I suggest that we stop trying to convince LtWorf that he is doing it wrong? I understand that his initial message was kind of a challenge (basically implying that Python is doing something wrong because it evolves). But I expect it’s more useful to discuss ways forward rather than trying to continue a “no you shouldn’t” - “yes I must” argument.
Sorry about that. I deleted my message because I saw your some messages are hidden by moderator and I didn’t want to participate in the flaming of this thread.
@LtWorf I understand you’re frustrated about the situation you’re experiencing with Python. However, that’s not a reason to be rude. If you want to post about your personal feelings and judgements about Python, do that in your own space. If you want to tell people to stop talking about it with you, do so politely, or flag it as off topic and don’t respond. This space is for having productive and professional discussions.
That goes for everyone else too, focus on the actual topic of this rather than trying to reply to that user.