Skip to content

Document style on naming env vars #1300

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 3 commits into from
Apr 2, 2024
Merged

Document style on naming env vars #1300

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aebbaac
Document style on naming env vars
hugovk Mar 25, 2024
fac41fe
Apply suggestions from code review
hugovk Mar 26, 2024
324fdc3
Update wording
hugovk Mar 27, 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
15 changes: 15 additions & 0 deletions developer-workflow/stdlib.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,7 @@ useful.

Adding a new module
-------------------

It must be stated upfront that getting a new module into the stdlib is very
difficult. Adding any significant amount of code to the stdlib increases the
burden placed upon core developers. It also means that the module somewhat
Expand Down Expand Up @@ -137,3 +138,17 @@ once the authors of the module sign
:ref:`contributor agreements <contributor_agreement>`.

.. _issue tracker: https://github.com/python/cpython/issues

Adding a new environment variable
---------------------------------

From Python 3.13 onwards, name environment variables with underscores for
readability and accessibility.

For example, use ``PYTHON_CPU_COUNT`` instead of ``PYTHONCPUCOUNT``.

See also:

* :ref:`python:using-on-envvars`
* `"Change environment variable style" Discourse discussion
<https://discuss.python.org/t/change-environment-variable-style/35180>`__
Loading