Pravic Ehysta added the comment:
Well, I deleted outdated registry keys, now it works fine.
Thanks for helping and I am going to close this issue since it isn't a bug.
--
resolution: -> not a bug
status: open -> closed
___
Python tracker
Steve Dower added the comment:
Were Python 3.5 and 3.4 installed into the same location? That would explain
some of the problems. It looks like it's finding it from the 3.4 key and then
skipping the 3.5 key because the path is the same - hence "py -3.5" doesn't
find it.
Also, we apparently
Pravic Ehysta added the comment:
d:\>py -3.5
launcher build: 32bit
launcher executable: Console
File 'C:\Users\owle\AppData\Local\py.ini' non-existent
File 'C:\Windows\py.ini' non-existent
Called with command line: -3.5
locating Pythons in 64bit registry
locate_pythons_for_key:
Steve Dower added the comment:
Can you do "set PYLAUNCH_DEBUG=1" and then run "py -3.4" again and paste the
full output?
Also, is there anything unusual about how you installed Python? Did you
customize any settings?
--
___
Python tracker
New submission from Pravic Ehysta:
d:\>py -3.5
Requested Python version (3.5) not installed
d:\>py -3.3
Requested Python version (3.3) not installed
d:\>py -3.4
Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits"
