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?

Maybe it makes sense to add a --basename-prompt flag to set the prompt to the current working directory's basename?

What does this buy you beyond using

--prompt $(basename $PWD)

? Perhaps I'm not understanding what you're getting at - how about an example of what you mean?

I like the idea and I think I will use it!

As it's a bit long to type, I'm searching if other shorter variants could be usefull like:

python3 -m venv --here
python3 -m venv --cwd
python3 -m venv --project

being the equivalent of python3 -m venv --basename-prompt venv, but I'm not satisfied with the names (and it enforces using "venv" as a directory name)...

@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).

Since there is already a --prompt available, I'd prefer a solution that allowed some special value(s) to be passed for this, e.g.

--prompt .

or perhaps

--prompt __curdir__

If it were . would we then always check if the prompt was a folder and then use the folder's name in that case? Or would it only apply to .?

As for __curdir__, it could work, but I don't know how easy would that be to remember or explain to new users compared to .?

My vote is to support . and make the rule that if you specify a folder it will use the basename automatically.

Any more feedback from anyone on the idea of using the basename of a directory if specified for --prompt?

New changeset 7d63780 by Vinay Sajip in branch 'master':
bpo-38901: Allow setting a venv's prompt to the basename of the current directory. (GH-17946)
7d63780

Can this now be closed, Vinay?