[Python-Dev] PEP 405 (venv) - why does it copy the DLLs on Windows
Vinay Sajip
vinay_sajip at yahoo.co.uk
Sat Mar 23 02:08:26 CET 2013
More information about the Python-Dev mailing list
Sat Mar 23 02:08:26 CET 2013
- Previous message: [Python-Dev] PEP 405 (venv) - why does it copy the DLLs on Windows
- Next message: [Python-Dev] PEP 405 (venv) - why does it copy the DLLs on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Moore <p.f.moore <at> gmail.com> writes: > I don't understand what this is saying - can someone clarify the > reason behind this statement? What is different about a > "non-system-wide installation" that causes this issue (I assume > "non-system-wide" means "not All Users")? The reason I ask is that > virtualenv doesn't do this, and I'm not clear if this is because of a > potential bug lurking in virtualenv (in which case, I'd like to find > out how to reproduce it) or because virtualenv takes a different > approach which avoids this issue somehow. One example of a non-system-wide installation is a source build of Python. PEP 405 venvs created from a source build should work in the same way as venvs created using an installed Python. Regards, Vinay Sajip
- Previous message: [Python-Dev] PEP 405 (venv) - why does it copy the DLLs on Windows
- Next message: [Python-Dev] PEP 405 (venv) - why does it copy the DLLs on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list