-
-
Notifications
You must be signed in to change notification settings - Fork 522
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
Multiple factors aren't respected #1433
Comments
Reversing the factors doesn't fix things.
|
I'm also aware that I can use factors in things like $ cat tox.ini
[tox]
minversion = 3.1
envlist = py37,functional,pep8
ignore_basepython_conflict = true
skipsdist = true
[testenv]
basepython = python3
whitelist_externals =
pip
deps =
requests
functional: requests-mock
commands =
pip freeze
python --version However, this doesn't scale for larger If either of my solutions are appropriate, I'd be happy to work on fixing this. |
This part should not exists:
There's no reason why you want to pull in an external pip.
This does not imply any factorials. You need tox environment names separated with the
This does not defines options for the functional factorial, but rather the functional environment. To better understand what's happening I recommend using
Yes, sadly that format is the only way you can define lines that apply to given factorials only. Things might get better with Does this helps you? |
Good point. We can ignore this though. I just whipped this together as an experiment.
Ahh, this is my mistake. I was confusing factors (factorials?) and environments. Thanks for the clarification.
It does, yes. I'll just stick with the above approach for now. |
This may be a misunderstanding of how
tox
is supposed to work on my end, so apologies if so. Take the followingtox.ini
file:If I run this with
tox -e py37
ortox -e functional
, things behave as expected. For example:My understanding of factors suggests that
tox -e functional-py36
should implicitly exist, becausepy36
is an auto-generated factor that implies some things (namely, the use ofbasepython=python3.6
instead ofpython3
). However, this is not the case as seen below. What's worse is that the request isn't even outright rejected - it works, but doesn't do what you'd expect:Note that
deps
fromtestenv:functional
isn't used. Rather, the value fromtestenv
is.I think that one of the following should happen:
functional
testenv and thepy36
testenv. As such, it should installrequests-mock
but usebasepython=python3.6
(preferred!)envlist
and isn't one of the auto-generated envsThe text was updated successfully, but these errors were encountered: