[issue15283] pyvenv says nothing on success

Roundup Robot added the comment: New changeset baf5ed391a7f by Vinay Sajip in branch 'default': Issue #15283: Updated pyvenv documentation to expand on activation. http://hg.python.org/cpython/rev/baf5ed391a7f -- ___ Python tracker

[issue15283] pyvenv says nothing on success

Senthil Kumaran added the comment: I think, the ``source bin/activate`` should be mentioned in the Docs at least. It should not require that a person carries this knowledge from somewhere else. At the moment, I do not see mention of it in the docs either - http://docs.python.org/dev/library/ven

[issue15283] pyvenv says nothing on success

Éric Araujo added the comment: > Creating a venv is useless if you don't ever activate it, right. This is a common misconception. Shell activation is only about putting the venv’s bin directory on the beginning of the PATH. It’s a purely optional convenience. Using a virtualenv can be done

[issue15283] pyvenv says nothing on success

Changes by Vinay Sajip : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue15283] pyvenv says nothing on success

Roundup Robot added the comment: New changeset 9c345b4bd97e by Vinay Sajip in branch 'default': Closes #15281, #15283: Don't make venv scripts executable, but copy source mode instead, and provide better help for pyvenv. http://hg.python.org/cpython/rev/9c345b4bd97e -- nosy: +python-de

[issue15283] pyvenv says nothing on success

Vinay Sajip added the comment: > It does one single thing and it has only a handful of options > (one of which is a no-op :-)). Perhaps it's a no-op only on your preferred operating system - that doesn't mean it's a no-op for everyone :-) I don't mind clarifying/expanding the help output, but

[issue15283] pyvenv says nothing on success

Martin v. Löwis added the comment: >> Using venv is not obvious in the first place. > > Well, why couldn't it *become* obvious. Because the notion of a "virtual environment" is inherently non-obvious. Is it like a virtual machine (and if so, like VMWare or like Java, both with virtual machines

[issue15283] pyvenv says nothing on success

Antoine Pitrou added the comment: > > Well, having to run "source bin/activate" is not obvious (unless you've > > already used virtualenv) > > Using venv is not obvious in the first place. Well, why couldn't it *become* obvious. It's not supposed to be a complicated piece of software. It does

[issue15283] pyvenv says nothing on success

Martin v. Löwis added the comment: > Well, having to run "source bin/activate" is not obvious (unless you've > already used virtualenv) Using venv is not obvious in the first place. so presumably, the user has read some documentation telling him what it is and how it's used. Presumably, that do

[issue15283] pyvenv says nothing on success

Antoine Pitrou added the comment: > The reason it says nothing on success is that it follows the general > philosophy of programs on Unix. Of course, there are exceptions, but > it's not obvious that pyvenv should say anything, and what it should > presume is the user's next likely step. Well,

[issue15283] pyvenv says nothing on success

Vinay Sajip added the comment: The reason it says nothing on success is that it follows the general philosophy of programs on Unix. Of course, there are exceptions, but it's not obvious that pyvenv should say anything, and what it should presume is the user's next likely step. As well as runn

[issue15283] pyvenv says nothing on success

Antoine Pitrou added the comment: > Command line utilities typically don't provide a success report. It depends which ones. Even Mercurial doesn't always abide by that rule (e.g. "hg clone" will tell you that it updates to the default branch). > Whether "source activate" is good advise or not

[issue15283] pyvenv says nothing on success

Martin v. Löwis added the comment: It should produce any output. Command line utilities typically don't provide a success report. Would you want "mkdir env" to say "created env directory; you can now cd into it", or "cat /etc/passwd" append "successfully displayed text file"??? There are exc

[issue15283] pyvenv says nothing on success

New submission from Antoine Pitrou : $ pyvenv-3.3 env $ It could tell me that I need to go into the directory and type "source bin/activate" (this is probably platform-dependent :-)). -- components: Demos and Tools, Library (Lib) messages: 164891 nosy: pitrou, vinay.sajip priority: nor