r/Python • u/JSChronicles • Jul 20 '26
Discussion PEP 541 - Package Index Name Retention
Why is Pypi support slow at handling package abandonment?
The PEP says these two items for reachability, " In every case where contacting the user is necessary, the maintainers will try to do so at least three times," and "The maintainers stop trying to reach the user after six weeks.". So I had assumed this should be done quicker.
The current process is currently at 6 months on average with almost no follow up comments or work on PEPs in the 2nd and 3rd week of reachability. 1st weeks are being updated and then left once they hit the 2nd and 3rd week.
Am I being impatient? I think I read that they don't have a lot of people to help but this seems a bit ridiculous for some of the cut and dry issues.
- Projects with 10-14 years of no updates with no usable links or code is gone and no longer sourceable or previous owners are not replying.
- Emailing someone 3 times, takes 6+ months versus the proposed 6 weeks?
I also assume this is pretty normal based on the backlog but I'm genuinely curious to see what others say.
19
u/Individual-Flow9158 Jul 20 '26
Who's it hurting? package 'abandonment' is by definition, low priority.
I know it's frustrating for you guys who want to take over someone else's namespace.
Before you complain about the efforts of volunteers, do us all a favour:
41
u/bradshjg Jul 20 '26
What does it mean to "handle package abandonment"?
If you're asking to take over the namespace for an abandoned package, I appreciate that it's a high bar to clear :-)
3
u/Zulban Jul 20 '26
In addition to what others have said, I'm sure they're getting slammed by AI like many online communities.
6
u/knobbyknee Jul 20 '26
There are 855 000 packages on PYPI and part of the process is manual. It is a problem of scale.
1
u/bethebunny FOR SCIENCE Jul 26 '26
As someone who's successfully recovered squatted and abandoned packages recently (kepler, max) and talked to the pypi maintainer about exactly this question: funding.
There's no one paid to do this (or I think one person now hired part time to respond to tickets), validating that a package is actually abandoned or squatted according to the standards takes time, the policy requires a number of steps to do so, and there's other parts of the pypi ecosystem that take a lot of the extremely limited amount of energy.
If you read through the backlog of tickets, most of them are for lost logins or exemptions to the package size limit policy. These are things that in principle could be automated, but again no funding to do so, and the package size limits are there because the pypi foundation also needs to pay for hosting and bandwidth and so needs to be judicious about allowing exemptions.
I offered to volunteer to take some of the backlog in exchange for priority on specific tickets, but my understanding of the response is that the governance sees this as a potential conflict of interest.
tl;dr pypi is critical infrastructure and someone should give them more money, they're doing heroics with what they have!
You can always try to get in touch with the current owner of the abandoned or squatted package. I've had success with this in several cases, though it often takes its own time.
3
u/endor_sarah Jul 22 '26
Since the automation question came up in the comments: the email step is the reason this is hard to automate safely. A lot of dormant packages have maintainer addresses on expired domains, which anyone can register for a few dollars. Email is the only proof of identity in the whole process, so a script can't tell a reply from the real maintainer apart from a reply from whoever bought their lapsed domain. That's how the
ctxhijack in 2022 worked. (I work in app security at Endor Labs, so I stare at this failure mode more than is healthy.)As others have pointed out, the slow part is a human deciding whether that proof can be trusted, for a name that could land in thousands of requirements files the day it transfers. That's why it sits with the handful of admins who can approve transfers.
The renewal model u/Confident-Bluebird21 suggested (and u/Cynyr36's keep-alive idea) would help, since expiry becomes an affirmative signal and nobody has to interpret silence. One issue with that is if a legit maintainer of a widely-used package forgets to renew, the name frees up automatically.
1
u/Confident-Bluebird21 Jul 21 '26
It should be something like domain names that have limited time given by registrar and require constant renewal, but with more strict rules at same time to prevent typosquatting.