Skip to content

PEP 396 was reclassifed as Withdrawn #1620

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 30, 2024
Merged

PEP 396 was reclassifed as Withdrawn #1620

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ff4f1f1
PEP 396 was reclassifed as Withdrawn
ncoghlan Oct 23, 2024
7d2a208
Fix another bit of wording that irked me
ncoghlan Oct 23, 2024
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
5 changes: 2 additions & 3 deletions source/discussions/versioning.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,16 +200,15 @@ import package versions are consistent with each other can review the
:ref:`single-source-version` discussion for potential approaches to doing so.

As import packages and modules are not *required* to publish runtime
version information in this way (see the rejected proposal in
version information in this way (see the withdrawn proposal in
:pep:`PEP 396 <396>`), the ``__version__`` attribute should either only be
queried with interfaces that are known to provide it (such as a project
querying its own version or the version of one of its direct dependencies),
or else the querying code should be designed to handle the case where the
attribute is missing [#fallback-to-dist-version]_.

Some projects may need to publish version information for external APIs
that don't meet the requirements for Python distribution package
:ref:`version specifiers <version-specifiers>`. Such projects should
that aren't the version of the module itself. Such projects should
define their own project-specific ways of obtaining the relevant information
at runtime. For example, the standard library's :mod:`ssl` module offers
multiple ways to access the underlying OpenSSL library version::
Expand Down
Loading