-
Notifications
You must be signed in to change notification settings - Fork 432
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
CI Tests failing (py 3.6 and 3.7) with version conflict: importlib_metadata #507
Comments
It’s likely due to nox requiring an incompatible importlib-metadata version. Would it help to populate the CI environment (the one containing nox, not the one nox creates) with the new pip resolver ( |
I don't quite understand what's going on, because when I run the tests locally using nox, there is no conflict on my local system. I'm not sure what the mention of |
Oh I see what's happening on my system. To run my nox I'm using python 3.8 even when the tests use other python versions. So I never have a need for Even @cs01's native-venv fork of nox still has virtualenv as a requirement. And virtualenv requires |
Looks like on my local system I can replicate the failure using python3.7 running nox. Also, Here is what causes the conflict.
|
Describe the bug
Github CI tests are now failing for python 3.6 and python 3.7 with a version conflict. It appears to be due to the requirement for
importlib-metadata < 2.0
and the providedimportlib-metadata
at v2.0.0.I'm having trouble reading this Traceback. Is this due to
virtualenv
requiringimportlib-metadata < 2.0
?How to reproduce
Expected behavior
The text was updated successfully, but these errors were encountered: