# PEP 763: Limiting deletions on PyPI **URL:** \ **Category:** Packaging\ **Tags:** pep\ **Created:** [October 28, 2024, 4:16pm UTC](https://discuss.python.org/t/pep-763-limiting-deletions-on-pypi/69487 "2024-10-28T16:16:03Z")\ **Posts on this page:** 2\ **Page:** 3
**Author:** ![ncoghlan](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ncoghlan/32/14266_2.png) [@ncoghlan](https://discuss.python.org/u/ncoghlan)\ **Post date:** [September 23, 2025, 6:18am UTC](https://discuss.python.org/t/pep-763-limiting-deletions-on-pypi/69487/44 "2025-09-23T06:18:35Z")
> [@dstufft](#): > > This is kind of an awkward situation, since it means that a PEP-worthy topic is blocked behind something that the PEP process can’t really control, but such is the world we live in 🙂 . I’d read that more as “A blanket prohibition on deletions would be unworkable in practice, and hence any realistic proposal needs to be focused on _limiting_ and/or _advertising_ deletions rather than disallowing them outright”. For example, we currently only have yanking (hidden from release listings, artifacts all remain) and hard deletion (release artifacts are immediately removed). What if we had notions like “pending deletion” or “ephemeral releases” where project maintainers indicate to the index operators that the artifacts can be deleted as necessary for quota management purposes, and this status is made visible in the API so tools can issue warnings when pinning to such releases. ---
**Author:** ![woodruffw](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/woodruffw/32/37228_2.png) [@woodruffw](https://discuss.python.org/u/woodruffw)\ **Post date:** [September 29, 2025, 1:40pm UTC](https://discuss.python.org/t/pep-763-limiting-deletions-on-pypi/69487/45 "2025-09-29T13:40:33Z")
This PEP is now formally withdrawn. Thank you all for the discussion and insights! [Previous page](https://discuss.python.org/t/pep-763-limiting-deletions-on-pypi/69487.md?page=2)