-
-
Notifications
You must be signed in to change notification settings - Fork 526
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
Conflicting basepython check fails for factor+testenv combination #1124
Comments
Thanks for reporting @ionelmc. If I plug this in
|
@obestwalter Run |
We have a similar issue on h5py, where we're also trying to test with 32-bit and 64-bit Python. To avoid telling tox that every Python is now the one we want to test on, I've had a go at writing a tiny plugin that uses an environment variable to control which one you use: https://github.com/takluyver/tox_appveyor This may change completely or be abandoned if we don't take this approach for h5py.
|
Feel free to open a PR against master and fix it. My available efforts at the moment are aimed at fixing this as part of #1394, but that probably will take a while (ETA September). |
@takluyver Your feature request is already discussed at #1149 |
I think this should work now fine on tox 4, so closing as such. |
For this given
tox.ini
:I get this sort of output:
This only happens if I have those
[testenv:pyXX-cover]
sections.Now why do I do it like that you might ask? Well ... on Windows I can specialize on different builds for the same python versions, eg, I want to test both 32bit and 64bit pythons, thus I run with both
TOXPYTHON=C:\Python37-x64\python.exe
andTOXPYTHON=C:\Python37\python.exe
(32bit).So after writing all that bugreport I realized I can just use factors for usedevelop but I'm submitting anyway, maybe someone has the same problem or you want to fix the check 😅 . Eg:
The text was updated successfully, but these errors were encountered: