/usr/bin in PATH
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Reproduce the behavior using the shown tox.ini, my-run script, and the two tox commands with different PATH values. Start by locating tox-current-env's PATH setup and verify whether /usr/bin is prepended only for --current-env. Done means the environment PATH takes precedence, either with /usr/bin omitted or appended after it.
Written by the indexing model from the issue text.
Description
Currently tox-current-env adds /usr/bin to PATH before the current PATH from environment:
$ cat my-run
#!/bin/sh
echo "PATH = $PATH"
$ cat tox.ini
[testenv]
allowlist_externals = my-run
commands = my-run
$ env - PATH=/tmp/test /usr/bin/tox-3.9 --current-env --no-provision --recreate -e py39
ROOT: tox-gh-actions won't override envlist because tox is not running in GitHub Actions
py39: remove tox env folder /tmp/test/.tox/py39
py39: commands[0]> my-run
PATH = /tmp/test/.tox/py39/bin:/usr/bin:/tmp/test
py39: OK (0.08=setup[0.04]+cmd[0.04] seconds)
congratulations :) (0.54 seconds)
$ env - PATH=/tmp/test /usr/bin/tox-3.9 --no-provision --recreate -e py39
ROOT: tox-gh-actions won't override envlist because tox is not running in GitHub Actions
py39: remove tox env folder /tmp/test/.tox/py39
py39: commands[0]> my-run
PATH = /tmp/test/.tox/py39/bin:/tmp/test
py39: OK (0.49=setup[0.46]+cmd[0.03] seconds)
congratulations :) (0.94 seconds)
$
This usually works okay, but in a case we need to override some command in /usr/bin by pointing PATH to some other location we simply can't.
Could you please either do not add /usr/bin to PATH at all, or add it after the PATH from environment?
Thank you.
- Dominant language
- Python
- Stars
- 26
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from fedora-python/tox-current-env
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
fedora-python/tox-current-env#86 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
fedora-python/tox-current-env#85 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fedora-python/tox-current-env#80 · 2 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
fedora-python/tox-current-env#79 · 2 comments ·
-
help wanted
Difficulty 3/5 1-2 days Newbie friendliness 35/100
fedora-python/tox-current-env#72 · 5 comments ·
All issues in fedora-python/tox-current-env
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
modelcontextprotocol/python-sdk#3648 ·
Maintainers usually reply within 1 day
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
VenetoStato/giorgio#6 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
EclipseFdn/open-vsx.org#13831 ·
Maintainers usually reply within 1 day