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
Export VIRTUAL_ENV
when executing python
inside a rye-managed project
#1043
Comments
VIRTUAL_ENV
when executing python
inside a rye-managed directoryVIRTUAL_ENV
when executing python
inside a rye-managed project
Do you have an example of a tool that is helped by this? |
Yes, https://github.com/JuliaPy/pyjuliapkg/blob/main/src/juliapkg/state.py#L61 |
Just as extra information for context, most python tools don't need this since if the currently running python is in a virtual environment that can be detected and the recommended way to detect does not use VIRTUAL_ENV, instead something along these lines https://stackoverflow.com/a/1883251
https://docs.python.org/3/library/venv.html#how-venvs-work Again, this is just context for the feature |
Makes sense. I opened up a separate issue in the source repository to hopefully address it at root. Just to make sure I understood, would you still consider exporting |
Maybe @mitsuhiko has better insight into what's best to do about that |
We do set |
I agree, and so do the the devs/maintainers of the conflicting package ( |
Not sure if this was intentionally left out, but it'd be great if
VIRTUAL_ENV
was set when executingpython
inside a rye-managed project so third-party programs can still find the.venv
path.The text was updated successfully, but these errors were encountered: