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.

Author vinay.sajip
Recipients raulcd, vinay.sajip, vstinner
Date 2015-02-02.08:03:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422864209.91.0.420911872409.issue23357@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the suggestion, but

(a) I don't think it's worth making this change.
(b) Your change still won't do the right thing in all cases.
(c) Your approach (of passing a parameter just for this) doesn't feel right.

For example, what if pyvenv is invoked using a symlink such as pyvenv-3.4? Your code would say "pyvenv", which seems "just as wrong" as saying "venv".

I don't believe the current state of affairs is really confusing (it hasn't been brought up before) - and even if it is, the right fix seems to be to mention in the documentation that the usage statement may vary slightly depending on exactly how the venv functionality is invoked.
History
Date User Action Args
2015-02-02 08:03:29vinay.sajipsetrecipients: + vinay.sajip, vstinner, raulcd
2015-02-02 08:03:29vinay.sajipsetmessageid: <1422864209.91.0.420911872409.issue23357@psf.upfronthosting.co.za>
2015-02-02 08:03:29vinay.sajiplinkissue23357 messages
2015-02-02 08:03:29vinay.sajipcreate