-
-
Notifications
You must be signed in to change notification settings - Fork 529
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.
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
tox cannot be started on itself with twice the same environment ( tox -e py27,py27) #111
Comments
Original comment by @hpk42 fix issue109 and fix issue111: multiple "-e" options are now combined → <<cset 3be5bca16f8b>> |
Original comment by @hpk42 Behaviour of -e has not changed, but can be set by passing True or False This parameter should come from a user specifyable default value _split_env() was factored out of class parseini to enable testing The issue #111: error on specifying same env twice ("tox -e py27,py27") → <> |
Original comment by @hpk42 Behaviour of -e has not changed, but can be set by passing True or False This parameter should come from a user specifyable default value _split_env() was factored out of class parseini to enable testing The issue #111: error on specifying same env twice ("tox -e py27,py27") → <<cset 96e1ba41e1c0>> |
Original comment by @hpk42 Behaviour of -e has not changed, but can be set by passing True or False This parameter should come from a user specifyable default value _split_env() was factored out of class parseini to enable testing The issue #111: error on specifying same env twice ("tox -e py27,py27") → <> |
Original comment by @AvdN This is caused by tox/_venv.py: _pcall updating the list 'args' in place. |
I am not sure it should run the same environment twice, but it should not throw an error:
This was tested on a fresh clone of tox:
The text was updated successfully, but these errors were encountered: