[issue15776] Allow pyvenv to work in existing directory

[Éric Araujo]

Éric Araujo added the comment:

> Well, changing it to do that means changing functionality, which is disallowed at this point in the release process.
I think people used to “virtualenv .” can see this as a regression between virtualenv and pyvenv, but if the PEP did not list that use case then it’s too late.  I’d suggest we even back out the “pyvenv --clear .” commit, which did not address the needs of the “virtualenv .” users.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15776>
_______________________________________