Chris Wood added the comment:
Ah, in that case:
- I guess the issue would have been that the python 3.5 installation I tried
(which was 3.5.0a1) had the vcruntime140.dll issue
- I've realised that the 3.5* installation puts Python on the beginning of the
PATH - whereas I was puttin
Chris Wood added the comment:
Apologies, there are typos in my final paragraph - 3.5.11 should just be 3.5,
and 3.5.12 should be 3.5.2
--
___
Python tracker
<http://bugs.python.org/issue27
Chris Wood added the comment:
https://www.python.org/downloads/
--
___
Python tracker
<http://bugs.python.org/issue27836>
___
___
Python-bugs-list mailin
New submission from Chris Wood:
Windows 7 / 64-bit / 4 Gb Ram / Intel i5 processor.
This seems to have been discussed intermittently in the past, but none of the
previous answers fixed my problem.
I installed 3.5, and when I tried running it (both from the Windows cmd line
and from the
