Skip to content

Fix for empty string value from pyvenv.cfg parsing #387

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jun 17, 2024
Merged

Fix for empty string value from pyvenv.cfg parsing #387

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dc30ce0
fixing pyvenv.cfg parsing
elebertus Jun 27, 2023
03a5376
Update segment-virtualenv.go
elebertus Nov 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion segment-virtualenv.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,14 @@ func segmentVirtualEnv(p *powerline) []pwl.Segment {
if env != "" {
cfg, err := ini.Load(path.Join(env, "pyvenv.cfg"))
if err == nil {
env = cfg.Section("").Key("prompt").String()
// python >= 3.6 the venv module will not insert a prompt
// key unless the `--prompt` flag is passed to the module
// or if calling with the prompt arg EnvBuilder
// otherwise env evaluates to an empty string, per return
// of ini.File.Section.Key
if pyEnv := cfg.Section("").Key("prompt").String(); pyEnv != "" {
env = pyEnv
}
}
}
}
Expand Down