Is there a reason that yank permissions | PyPA | Page 1

supple aspen Nov 5, 2022, 11:24 PM

#

I don't think there's a reason. Generally maintainers are limited from 'destructive' actions, but since un-yanking is possible, I think it would be reasonable to extend this permission to maintainers. Could you open an issue at https://github.com/pypi/warehouse/issues ?

GitHub

Issues · pypi/warehouse

The Python Package Index. Contribute to pypi/warehouse development by creating an account on GitHub.

candid crescent Nov 6, 2022, 12:15 AM

#

Great, will do that. ninja 1.11.1 is sadly segmentation faulting on Linux. 😦

#

Unfortionaly, it's likely a bit of a project, as maintainers don't see the manage UI at all and currently that's the only place yanking shows up.

supple aspen Nov 6, 2022, 1:09 AM

#

Ah, right. That's probably the main reason why then: it was easiest

candid crescent Nov 6, 2022, 3:35 AM

#

FYI, ninja's manylinux1 wheels segfaulted on newer platforms. manylinux2010 work & was able to add those, so the 1.11.1 release was fixed. Still would have been really helpful to have been able to yank. SciPy and a bunch of other things were broken for a few hours today. I'll write up a proper issue in the next couple of days!

supple aspen Nov 6, 2022, 3:52 AM

#

Sounds like a good reason (amongst others) to promote some maintainers to project owners 🙂 If the existing maintainer is unresponsive, this could be done via a PEP 541 request.

candid crescent Nov 6, 2022, 4:13 AM

#

In this case, project owners are only responsive on weekdays and some maintainer had the brilliant idea of releasing on a weekend when there are fewer users. 😉 (actually wasn't me this time, but was me last time) I rather expect that will be the fix in our case, but I think it really needs to be eventually fixed in the future so that anyone who uploads a release can then yank it if it's a disaster. Even if a maintainer could only yank a release they made, that would be a big improvement.

#Is there a reason that yank permissions