You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Starship is awesome! Thanks! This is not related to a problem.
Describe the solution you'd like
When activating a python virtual environment created locally, Starship awesomely reaches back to the project directory for the name of the virtualenv in the prompt, rather than just calling it .venv. For example, it correctly looks like this (note, I intentionally rearranged the order of my prompt to put the virtualenv first):
I couldn't find it in the documentation or issues list, but I'd like to suppress the version number after the name of the virtualenv. In my example, the virtualenv would just be (notebooks)
Describe alternatives you've considered
Maybe a way to tweak the virtualenv variable in the format option of the python module?
The text was updated successfully, but these errors were encountered:
Why would you want that, isn't it better if you know the python version your environment is using? i get that you can just use python --version but still.
Just a preference. I run multiple virtual environments, but usually only one version of Python (only occasionally use pyenv).
The version number in the prompt seems to be only triggered by a virtual environment called .venv. If I create a virtual environment with another name, and activate it, the name shows up in the prompt, but the version number doesn't.
Just a preference. I run multiple virtual environments, but usually only one version of Python (only occasionally use pyenv).
The version number in the prompt seems to be only triggered by a virtual environment called .venv. If I create a virtual environment with another name, and activate it, the name shows up in the prompt, but the version number doesn't.
What's the full name of your venv when you're "not using .venv"? If it's auto generated for you by a tool, there's a good chance the venv name itself contains the python version and that's what you're seeing.
Feature Request
Is your feature request related to a problem? Please describe.
Starship is awesome! Thanks! This is not related to a problem.
Describe the solution you'd like
When activating a python virtual environment created locally, Starship awesomely reaches back to the project directory for the name of the
virtualenv
in the prompt, rather than just calling it.venv
. For example, it correctly looks like this (note, I intentionally rearranged the order of my prompt to put thevirtualenv
first):I couldn't find it in the documentation or issues list, but I'd like to suppress the version number after the name of the
virtualenv
. In my example, thevirtualenv
would just be(notebooks)
Describe alternatives you've considered
Maybe a way to tweak the
virtualenv
variable in theformat
option of thepython
module?The text was updated successfully, but these errors were encountered: