Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 17 additions & 9 deletions peps/pep-0534.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Title: Improved Errors for Missing Standard Library Modules
Author: Tomáš Orsava <tomas.n@orsava.cz>,
Petr Viktorin <encukou@gmail.com>,
Alyssa Coghlan <ncoghlan@gmail.com>
Status: Deferred
Status: Withdrawn
Type: Standards Track
Created: 05-Sep-2016
Post-History:
Expand All @@ -22,16 +22,24 @@ and providing more informative error messages to users when attempts to import
standard library modules fail.


PEP Deferral
============
PEP Withdrawal
==============

The authors have withdrawn this PEP as the core ideas have been implemented over
time. The relevant features include the :data:`sys.stdlib_module_names`
API for listing standard library modules, the
:external+py3.15:option:`--with-missing-stdlib-config`
configure option for distributors to provide custom error messages,
and improved :exc:`ModuleNotFoundError` error messages for missing
:term:`standard library` modules, for example:

The PEP authors aren't actively working on this PEP, so if improving these
error messages is an idea that you're interested in pursuing, please get in
touch! (e.g. by posting to the python-dev mailing list).
.. code-block:: pycon

The key piece of open work is determining how to get the autoconf and Visual
Studio build processes to populate the sysconfig metadata file with the lists
of expected and optional standard library modules.
>>> import zlib
Traceback (most recent call last):
File "<python-input-0>", line 1, in <module>
import zlib
ModuleNotFoundError: Standard library module 'zlib' was not found


Motivation
Expand Down