Allow to declare inside tox.ini that some environments need to not use a venv
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, tooling
Research direction
Start by tracing how the current command-line switch activates the plugin and how tox.ini environments are represented. Define the configuration shape for selecting environments that should not use a virtual environment, while preserving existing behavior for other environments; done means the option works from tox.ini without the command-line switch.
Written by the indexing model from the issue text.
Description
As this plugin scope is to bypass the usage of a venv with tox, I do have a highly related use-case: I want to add some tox environments in tox.ini file that will not use any venv.
Basically this is asking for another way to activate this plugin instead of the command line switch.
This could prove very useful for using tox as a more generic build tool.
- 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 ·
-
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 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fedora-python/tox-current-env#69 · 1 comment ·
All issues in fedora-python/tox-current-env
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
FuRongJun-1999/dsh-memory#56 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pgadmin-org/pgadmin4#10503 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#3857 ·
-
needs-ac
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Ikalus1988/MisakaNet#2845 ·
Maintainers usually reply within 1 day
-
bug connectors operations
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyinfra-dev/pyinfra#1989 ·
Maintainers usually reply within 3 days