# Handling modules on PyPI that are now in the standard library?

**URL:** <https://discuss.python.org/t/handling-modules-on-pypi-that-are-now-in-the-standard-library/27071>\
**Category:** Core Development\
**Created:** [May 25, 2023, 4:54am UTC](https://discuss.python.org/t/handling-modules-on-pypi-that-are-now-in-the-standard-library/27071 "2023-05-25T04:54:13Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![CAM-Gerlach](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/cam-gerlach/32/3688_2.png) [@CAM-Gerlach](https://discuss.python.org/u/CAM-Gerlach)\
**Post date:** [May 27, 2023, 6:00am UTC](https://discuss.python.org/t/handling-modules-on-pypi-that-are-now-in-the-standard-library/27071/11 "2023-05-27T06:00:50Z")

</div>

Since it seems [as I just posted about on the relevant `nntplib` thread](https://discuss.python.org/t/allow-nntplib-on-pypi/25786/28) that at least one exception to the standard PyPI policy was apparently made recently to hand over an existing stdlib name to a third party project, and this topic focuses specifically on PyPI projects that were superseded by standard library modules and I don’t want to drag things further off topic, I’ve opened a new thread in #Packaging to discuss and hopefully come to consensus on a coherent policy on this “opposite” case, in collaboration with the PyPI admins involved:

> [@PyPI policy on handing over protected standard library names to third party maintainers](https://discuss.python.org/t/pypi-policy-on-handing-over-protected-standard-library-names-to-third-party-maintainers/27143):
>
> Up until now, as far as I’m aware names of modules and import packages in the Python standard library are not permitted for new PyPI uploads, in order to protect against the obvious security implications and user mistakes. However, with the [PEP 594 mass deprecation and removal of obsolescent stdlib modules](https://discuss.python.org/t/pep-594-has-been-implementated-python-3-13-removes-20-stdlib-modules/27124/), questions have arisen on how to handle third party requests to claim these protected names in order to publish their own standalone versions of these modules, including: [Allow nntplib on P…](https://discuss.python.org/t/allow-nntplib-on-pypi/25786/)

Also, @dstufft any particular reason this is in #Core Development and shouldn’t be moved to #Packaging ? Seems like its much more of a packaging concern than something directly related to the development of those modules in CPython, and would attract more relevant interest being moved there, but there could be something I’m missing here.

---

_[View the full topic](https://discuss.python.org/t/handling-modules-on-pypi-that-are-now-in-the-standard-library/27071)._
