Skip to content
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

windows + conda : nox using an interpreter that does not exist #352

Closed
omry opened this issue Oct 13, 2020 · 3 comments
Closed

windows + conda : nox using an interpreter that does not exist #352

omry opened this issue Oct 13, 2020 · 3 comments
Labels
bug upstream This is a bug in one of our dependencies

Comments

@omry
Copy link
Contributor

omry commented Oct 13, 2020

This is probably related to some change in my CI, but I am having a hard time figuring it out.

Describe the bug
nox is trying to use a Python interpreter that is not there:

(hydra) PS C:\Users\circleci\project> where.exe python
where.exe python
C:\tools\miniconda3\envs\hydra\python.exe
(hydra) PS C:\Users\circleci\project> nox -s lint-3.8
nox -s lint-3.8
nox > Running session lint-3.8
nox > Creating virtual environment (virtualenv) using python.EXE in .nox\lint-3-8
Operating system        :       Windows
NOX_PYTHON_VERSIONS     :       ['3.6', '3.7', '3.8']
PLUGINS                 :       ['ALL']
SKIP_CORE_TESTS         :       False
FIX                     :       False
VERBOSE                 :       0
INSTALL_EDITABLE_MODE   :       0
nox > Command c:\tools\miniconda3\envs\hydra\python.exe -m virtualenv C:\Users\circleci\project\.nox\lint-3-8 -p C:\tools\miniconda3\envs\hydra\python.EXE failed with exit code 1:
FileNotFoundError: [Errno 2] No such file or directory: 'c:\\tools\\miniconda3\\envs\\hydra\\Lib\\venv\\scripts\\nt\\python.exe'
nox > Session lint-3.8 failed.
(hydra) PS C:\Users\circleci\project> 

How to reproduce
This is only happening in CircleCI, so I am not sure what is actually causing it (I tested on Windows 10 with conda and it works there).
It was also working fine until it broke without any apparent change.

Any hints on how to debug or workaround?

@omry omry changed the title Nox recognizing a Python interpreter that does not exist in windows + conda : nox using an interpreter that does not exist Oct 13, 2020
@drewgilliam
Copy link

FYI - conda and virtualenv 20.0.34 aren't playing well together. see pypa/virtualenv#1986 and ContinuumIO/anaconda-issues#12094

@omry
Copy link
Contributor Author

omry commented Oct 20, 2020

This explains it, thanks @drewgilliam.
One of the comments suggest virtualenv==20.0.33 as a workaround, I will give it a shot as a temporary solution.

@theacodes theacodes added bug upstream This is a bug in one of our dependencies labels Nov 19, 2020
@theacodes
Copy link
Collaborator

For now we'll just wait for virtualenv to fix this unless y'all think we can do anything here to mitigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug upstream This is a bug in one of our dependencies
Development

No branches or pull requests

3 participants