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
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2020-01-14.23:57:53.719>created_at=<Date2019-11-23.22:28:34.409>labels= ['type-feature', 'library']
title='[venv] Add a CLI flag to venv to use the pwd basename as the prompt'updated_at=<Date2020-01-14.23:57:53.718>user='https://github.com/brettcannon'
I did a Twitter poll to see if there was consistent naming of the directory people created a virtual environment into when done locally to code (the answer is no). But a common theme was people not liking that the prompt defaults to the name of the directory that the virtual environment is in and seem to prefer for it to be os.path.basename(os.getcwd()).
Maybe it makes sense to add a --basename-prompt flag to set the prompt to the current working directory's basename?
@vinay you got exactly what I mean. I had to actually teach a ton of people that shell trick with basename and pwd on Twitter, that trick doesn't seem to be something people know about, and yet a ton of people seem to be creating virtual environments with prompts manually specified like that.
Plus that trick varies from shell to shell and we already have enough issues just explaining to people how to activate between Windows and UNIX and then between even shells on the same OS.
So this is entirely for convenience.
@julien default directory names is an entirely separate topic as people can't agree on the default name (e.g. I prefer .venv as my default).