New submission from Julien Palard <julien+pyt...@palard.fr>:
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.
----------
messages: 404132
nosy: mdk
priority: normal
severity: normal
status: open
title: [idea] Successfully creating a venv could print a message.
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue45501>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
