[issue38537] Python 2.7.17 reports itself as 2.7.16

[PEW's Corner]

PEW's Corner <pewscorner at gmail.com> 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 your hypothesis is probably correct.

Considering that the user has no easy way to make the correct choice, nor to anticipate the consequences of a wrong choice, the term "user error" doesn't feel right. :-) But I completely understand why you wouldn't want to put much effort into fixing something that is almost dead, and at least *I* now know how to fix the problem when it happens again.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________