We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using virtual environment for Python. The last two lines of pyvenv.cfg for this app are:
command = C:\Python\.pyenv\pyenv-win\versions\3.11.7\python.exe -m venv c:\Python\x\a prompt = Warranties-venv
command = C:\Python\.pyenv\pyenv-win\versions\3.11.7\python.exe -m venv c:\Python\x\a
prompt = Warranties-venv
I get this prompt when the virtual environment is activated (without special chars):
Warranties on ? master via ? v3.11.7 (.venv)
but if the last two lines of pyvenv.cfg are:
command = C:\Python\.pyenv\pyenv-win\versions\3.11.7\python.exe -m venv c:\Python\X\a prompt = Warranties-venv
command = C:\Python\.pyenv\pyenv-win\versions\3.11.7\python.exe -m venv c:\Python\X\a
With just the single character change I get this prompt when the virtual environment is activated(without special chars):
Warranties on ? master via ? v3.11.7 (Warranties-venv)
Please note that the two directories at the end of the "command" line:
c:\Python\x\a c:\Python\X\a
c:\Python\x\a
c:\Python\X\a
do not exist.
Somehow I was able to find a way to change this behaviour with a single byte change.
The prompt I would like to appear should reflect the prompt setting in pyvenv.cfg that is: Warranties on ? master via ? v3.11.7 (Warranties-venv)
I suspect that fn get_prompt_from_venv in python.rs has a logical flaw but it was not obvious to me.
fn get_prompt_from_venv
$scripts = "$(split-path $PROFILE)\Scripts" #$modules = "$(split-path $profile)\Modules" $docs = $(resolve-path "$Env:userprofile\documents") $desktop = $(resolve-path "$Env:userprofile\desktop") Invoke-Expression (&starship init powershell) Import-Module -Name Terminal-Icons
# stored at C:\DevTools\Starship\starship.toml # pointed to by STARSHIP_CONFIG command_timeout = 2000 [aws] disabled = true
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Current Behavior
Using virtual environment for Python.
The last two lines of pyvenv.cfg for this app are:
command = C:\Python\.pyenv\pyenv-win\versions\3.11.7\python.exe -m venv c:\Python\x\a
prompt = Warranties-venv
I get this prompt when the virtual environment is activated (without special chars):
Warranties on ? master via ? v3.11.7 (.venv)
but if the last two lines of pyvenv.cfg are:
command = C:\Python\.pyenv\pyenv-win\versions\3.11.7\python.exe -m venv c:\Python\X\a
prompt = Warranties-venv
With just the single character change I get this prompt when the virtual environment is activated(without special chars):
Warranties on ? master via ? v3.11.7 (Warranties-venv)
Please note that the two directories at the end of the "command" line:
c:\Python\x\a
c:\Python\X\a
do not exist.
Somehow I was able to find a way to change this behaviour with a single byte change.
Expected Behavior
The prompt I would like to appear should reflect the prompt setting in pyvenv.cfg
that is:
Warranties on ? master via ? v3.11.7 (Warranties-venv)
Additional context/Screenshots
Possible Solution
I suspect that
fn get_prompt_from_venv
in python.rs has a logical flaw but it was not obvious to me.Environment
Relevant Shell Configuration
Starship Configuration
The text was updated successfully, but these errors were encountered: