-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add vox enter
command
#5
Comments
Hm. Could be done with caching state ( |
note: vox has an 'enter' command which is an alias of activate. |
@astronouth7303 Could you elaborate a bit more of what you mean? I use something like this with xonsh-autoxsh
Since it's usually a good idea to use a new virtualenvironment for every project this snipped kinda serves the same purpose. |
I mean applying a virtual environment to your xonsh session. Or maybe spawning a xonsh shell in the environment? Either way, it involves crossing environments and other weirdness, so it's certainly non-trivial. |
@AstraLuma |
No, the python contents, not just the commands. |
could you elaborate on this? I still don't get it. |
Add the python environment of the venv to xonsh's python environment. So you have a repl kinda matching the project you're working on. |
That can be done by adding site-packages to the PYTHONPATH of the xonsh's venv. I think it should be a separate xontrib than vox itself. It just manages the virtualenv, and to facilitate imports from the current env, seems a different thing. |
Basically, a magic command that will apply the named venv to the prompt, or create a new prompt in the venv, without having to install xonsh & xontribs into the venv.
For community
⬇️ Please click the 👍 reaction instead of leaving a
+1
or 👍 commentThe text was updated successfully, but these errors were encountered: