Closed rcpeene closed 6 months ago
Hi @rcpeene - thanks for taking the time to report this and apologies for being slow to respond.
Windows is awkward. I've found that the libraries we depend on in the jupyter stack (e.g. nbclient, jupyter-server) are less reliable and less tested on Windows.
As such we don't test on windows (IIRC), yet many people still use nbmake on it.
I'm unable to look into this right now but I'd suggest dropping this issue into our discord and seeing if other users can support: https://discord.com/invite/QFjCpMjqRY
I had had other environment problems with other Python projects at the same time; Not a real fix to the problem but a total reinstallation of Python fixed the issue. I suspect it has to do with windows looking at two different installations of Python
yes the interaction between jupyter and python binaries on the file system can be brittle, especially with multiple installations/virtual environments.
Glad that's fixed!
Describe the bug pytest can't seem to find my basic python3 kernel. when running
pytest --nbmake -n=auto ./docs/projects/illusion.ipynb
the test fails and I receiveNo such kernel named python3
To Reproduce I am not sure what steps would be required to reproduce; I simply installed nbmake and pytest-xdist and run the above command within the local clone of my repo https://github.com/AllenInstitute/openscope_databook.git
Expected behavior I expect the test to pass
Traceback
Environment