Allow to pass environment variables to tox environments
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 7
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
So:
[test]
pass_env =
MY_CUSTOM_VARIABLE
ANOTHER_ONE
PYTHONWARNINGS
Specially the last one, when not wishing to remove deprecation warnings helps a lot in not drowning within them, when you are actually looking at why your tests failed 😅
And what's best: that we allow passing them, does not mean that we are enabling them, you should still do:
export PYTHONWARNINGS="ignore::DeprecationWarning"
✨
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the repository's tox configuration and inspect how the [test] environment is defined, then check any existing tox-related validation or documentation. Done means users can list variables such as MY_CUSTOM_VARIABLE, ANOTHER_ONE, and PYTHONWARNINGS in pass_env without those variables being enabled automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100