➜
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.
Created on 2015-09-15 08:10 by mgedmin, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg250733 - (view) | Author: Marius Gedminas (mgedmin) * | Date: 2015-09-15 08:10 | |
1. Install Python 3.5 using the official Windows installer 2. Get a shell 3. python -m ensurepip (because the installer didn't install pip for me -- is that another bug? I thought the installer was supposed to run ensurepip for me? Is it fallout from bug 25117?) 4. python -m pip install virtualenv (gets me version 13.1.2) 5. python -m virtualenv env I expect: a virtualenv in ./env I get: a GUI error dialog saying "The program can't start because VCRUNTIME140.dll is missing from your computer." |
|||
| msg250745 - (view) | Author: Eryk Sun (eryksun) *  |
Date: 2015-09-15 08:48 | |
virtualenv fails to copy vcruntime140.dll. Use the standard library's venv module instead. |
|||
| msg250770 - (view) | Author: Marius Gedminas (mgedmin) * | Date: 2015-09-15 13:48 | |
Thank you for the pointer! It's hard to tell which software component is at fault when multiple components fail to collaborate. I cannot choose to use venv because I'm actually using tox, which runs virtualenv for a bunch of Python versions, some of which don't even have venv. I've filed a virtualenv bug: https://github.com/pypa/virtualenv/issues/796 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:21 | admin | set | github: 69306 |
| 2015-09-15 13:48:37 | mgedmin | set | messages: + msg250770 |
| 2015-09-15 08:48:34 | eryksun | set | status: open -> closed nosy: + eryksun messages: + msg250745 resolution: third party stage: resolved |
| 2015-09-15 08:10:15 | mgedmin | create | |