Document style on naming env vars #1300
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
After reviewing the rest of the page, I think this new section should also cover when is it ok to add new envvars and how to do it, even though you might want to do that in a separate PR. |
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
hugovk
commented
Mar 27, 2024
JacobCoffee
approved these changes
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1285.
I wasn't sure where to put it, so went for
developer-workflow/stdlib.html.Is there a better place?
馃摎 Documentation preview 馃摎: https://cpython-devguide--1300.org.readthedocs.build/