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

Terminal Environment #10006

Open
Darin-RVI opened this issue Mar 25, 2021 · 3 comments
Open

Terminal Environment #10006

Darin-RVI opened this issue Mar 25, 2021 · 3 comments

Comments

@Darin-RVI
Copy link

Great tool, I'm still a bit of a noob. I work in a server based environment and each job is a separate python virtual environment with associated Jupyter Lab sessions.

When you open a terminal (Great Feature) it drops you in the correct folder but not in the virtual environment. Would it be possible to active the virtual environment?

@jasongrout
Copy link
Contributor

In general, an environment could be a pip virtual environment, a conda virtual environment, or any number of other things. I think the difficulty here would be figuring out what the "correct" thing to do here.

Perhaps the thing to do is to provide a setting for code to execute at the start of a terminal session? Then you could have whatever logic you want in place?

@Darin-RVI
Copy link
Author

@jasongrout - Thanks for responding. :) That's a very good point. What about a concept similar to the .bashrc, .bash_profile, .profile, autoexec.bat, etc. If the user drops a .jlt_profile file that the terminal would execute. The user would be able to define what happens as needed.

@krassowski
Copy link
Member

krassowski commented Apr 10, 2021

Also see a previous issue on this topic (for conda) here: #5290

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

No branches or pull requests

3 participants