Message258934
By design, the stdlib venv functionality expects to work from an installed Python. However, the Python in a virtualenv venv is not an installed Python - it copies some files from the Python it was installed from and does various other hacks in order to work (I'm not using 'hack' as a pejorative here - it's just what virtualenv has to do).
Thus, you cannot use venv to create an environment from a virtualenv venv's Python. For this to work seamlessly, there would probably need to be coupling between venv and virtualenv - virtualenv has potentially to be updated with additional hacks every time there is a new Python release, in order to keep working.
It doesn't make sense to couple the stdlib closely with a third-party package. Does it work the other way around? I realise this doesn't help you with tox, and of course tox has to use virtualenv because of supporting older versions of Python ... |
|
Date |
User |
Action |
Args |
2016-01-26 00:06:24 | vinay.sajip | set | recipients:
+ vinay.sajip, carljm, dstufft, The Compiler, André Caron |
2016-01-26 00:06:24 | vinay.sajip | set | messageid: <1453766784.09.0.242659838177.issue26203@psf.upfronthosting.co.za> |
2016-01-26 00:06:24 | vinay.sajip | link | issue26203 messages |
2016-01-26 00:06:24 | vinay.sajip | create | |
|