I try to avoid env, venv, etc for my virtualenvs. It makes them too hard to distinguish between them when they're activated.

I'll agree with this sentiment, in general. The reason why I usually stick with "venv" is that I try to force myself to single-task, so I'm never actively juggling environments. The (venv) in the prompt is just there to let me know what I'm in an active virtual environment. That said, I think you're probably right.

Perhaps you're right. Having a single, short string is probably useful. It enforces a discipline of focus.

I think venv is fine as a generic example. Anything is better than virtualenv ., which everyone was pushing for years. shudders