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
In a Python 2 repository python
gives you Python 3
#698
Comments
related/original issue https://github.com/jupyterhub/binderhub/issues/871 |
Activating the So 👍 on activating that in the terminal by default, see my attempt below. Digging into the issue AFAICS the conda environment should be activated via file But looking at the debug output of repo2docker locally, that file does not seem to be called. Should it be picked up by Could the problem be that
When I run
Note that in the listing, Looking at the path in a repo where I encountered this issue (see https://discourse.jupyter.org/t/creating-environment-yml-for-python-2-via-binder/1609), I think there might be a bug in the third path element, which reads
Solution? I have made the following changes, and the desired kernel is then active in the terminal rightaway (the Click to expand
I also changed the docs to not use Happy to run tests (not done yet!) and potentially add a test if you think this goes in the right direction. |
Bug description
In a repo with Python 2 selected via a
runtime.txt
the commandpython
launches Python 3.Expected behaviour
python
should launch version 2.How to reproduce
python
I think it is because of the order in which environments appear on the search path:
Not sure if this is a bug or merely "surprising behaviour" that needs documenting. Maybe we could write down somewhere why
/srv/conda/bin
does come before/srv/conda/envs/kernel/bin
to help people understand why it is this way.The text was updated successfully, but these errors were encountered: