[issue38537] Python 2.7.17 reports itself as 2.7.16

PEW's Corner added the comment: Yes, the dll now seems to have ended up in c:\windows\syswow64. I have no idea whether I chose "just for me" or "all users" last time (this is a general irritant when having to manually update software on Windows), but I did choose "all users" this time, so

[issue38537] Python 2.7.17 reports itself as 2.7.16

Steve Dower added the comment: Exactly where were the DLLs installed? If you had previously done "just for me" and then this time did "all users", the python27.dll for 2.7.17 will be in C:\Windows\SysWow64, which has lower priority than the one in the same directory. I won't be fixing or

[issue38537] Python 2.7.17 reports itself as 2.7.16

Change by SilentGhost : -- components: +Windows nosy: +paul.moore, tim.golden, zach.ware ___ Python tracker ___ ___

[issue38537] Python 2.7.17 reports itself as 2.7.16

Change by Karthikeyan Singaravelan : -- nosy: +benjamin.peterson, steve.dower ___ Python tracker ___ ___ Python-bugs-list mailing

[issue38537] Python 2.7.17 reports itself as 2.7.16

PEW's Corner added the comment: After experimenting a bit more, I found that the python27.dll is NOT part of the new installation, but is also NOT removed on upgrade or when uninstalling. After I manually deleted this dll, the new installation correctly reports itself as 2.7.17. So the

[issue38537] Python 2.7.17 reports itself as 2.7.16

New submission from PEW's Corner : After upgrading Python 2.7.16 to 2.7.17 using the Windows x86 MSI installer, the new Python still reports itself as version 2.7.16: D:\Python27>.\python.exe Python 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] on win32 Type