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

To do: handle relative paths or directory-specific kernels #199

Open
mcg1969 opened this issue Dec 5, 2020 · 0 comments
Open

To do: handle relative paths or directory-specific kernels #199

mcg1969 opened this issue Dec 5, 2020 · 0 comments

Comments

@mcg1969
Copy link
Collaborator

mcg1969 commented Dec 5, 2020

Suppose conda's envs_dirs configuration includes a relative path among its entries (whether in the .condarc, in an environment variable, or anywhere else it can be configured). This means that conda's environment search depends on the directory you are currently in.

This actually has some genuinely good uses. For instance, suppose you add ./envs to your envs_dirs path. Then you now have a simple mechanism for finding project-specific environments. Just create a subdirectory named envs in your environment, then do conda create -p envs/<name> ..., and conda will automatically start picking it up when you are in that directory.

It would be great of nb_conda_kernels could handle this elegantly. To do so, it would need to be notified whenever the user moves into a new directory in the Jupyter file browser, and rescan the environment list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant