This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: [idea] Successfully creating a venv could print a message.
Type: Stage:
Components: Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: mdk, steven.daprano
Priority: normal Keywords:

Created on 2021-10-17 10:10 by mdk, last changed 2022-04-11 14:59 by admin.

Messages (2)
msg404132 - (view) Author: Julien Palard (mdk) * (Python committer) Date: 2021-10-17 10:10
I realized that many students get surprised by `python -m venv .venv` not printing anything, a few even think it completly failed.

I'm OK teaching them this is normal, as `mv`, `cp`, `rm`, `django-admin startproject`, ... does not print neither when they succeed.

But I fear many other Python users could be surprised too and not have a teacher around to reassure them.

I kept this as a status-quo for years but thinking of it today I though « And why not telling them how to activate the venv? »

Would'nt it be great to have:

    $ python3 -m venv .venv
    Environment created successfully, activate it using:

        source .venv/bin/activate

or

    PS C:\Users\Admin> python3 -m venv .venv
    Environment created successfully, activate it using:

        .venv\Scripts\Activate.ps1

and so on?

A `-q`/`--quiet` could be added for scripts creating venvs.
msg404267 - (view) Author: Steven D'Aprano (steven.daprano) * (Python committer) Date: 2021-10-19 03:39
This may be an example of the problem:

https://discuss.python.org/t/why-does-venv-not-work-on-my-windows-system/11167

The poster there hasn't responded yet, so it isn't clear what is the actual issue is. But it looks suspiciously like a failure to realise that the venv actually did work.
History
Date User Action Args
2022-04-11 14:59:51adminsetgithub: 89664
2021-10-19 03:39:12steven.dapranosetnosy: + steven.daprano
messages: + msg404267
2021-10-17 10:10:17mdkcreate