New submission from Marius Gedminas:
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
eryksun added the comment:
virtualenv fails to copy vcruntime140.dll. Use the standard library's venv
module instead.
--
nosy: +eryksun
resolution: -> third party
stage: -> resolved
status: open -> closed
___
Python tracker
Marius Gedminas added the comment:
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
