2

I have installed python 2.7 on windows 64 bit. But python is telling me that it is installed on windows 32 bit. See image below.

enter image description here

Where as my system is 64 bit as shown in the image below.
enter image description here

Amritbir Singh Gill
  • 366
  • 1
  • 3
  • 12
  • 1
    no the version of python is 64 bit. see first image. – Amritbir Singh Gill Sep 19 '15 at 17:12
  • 3
    http://stackoverflow.com/questions/3411079/why-does-the-python-2-7-amd-64-installer-seem-to-run-python-in-32-bit-mode – Stepan Tsymbal Sep 19 '15 at 17:14
  • Thank you @StepanTsymbal – Amritbir Singh Gill Sep 19 '15 at 17:19
  • `win32` is an architecture not a bitness. You will see messages issued by 64-bit executable that talk about `win32`. This is normal. – BoarGules Jan 03 '20 at 20:26
  • @BoarGules: according to [this](https://stackoverflow.com/questions/17757819/what-does-the-python-version-line-mean), `win32` just seems to be a misleading name for "Windows platform". It's not an architecture in the sense of a particular CPU... – FObersteiner Jan 03 '20 at 20:52
  • Does this answer your question? [What does the Python version line mean?](https://stackoverflow.com/questions/17757819/what-does-the-python-version-line-mean) – FObersteiner Jan 03 '20 at 20:53
  • @MrFuppes It is a software architecture in the sense that it was devised to set `win32` apart from its predecessor 16-bit OS. That involved changing the signatures of every function in the huge Windows API to accept 32-bit instead of 16-bit quantities. Whether that counts as a different architecture is a matter of opinion, but my main point stands. `win32` in messages has nothing to do with the bitness of the Python executable or the DLLs that it calls. 64-bit executables still complain when asked to call 32-bit DLLs, and though the messages vary, they may still say *not a valid `win32` file*. – BoarGules Jan 03 '20 at 21:07
  • @BoarGules - thanks for the clarification. "*win32 in messages has nothing to do with the bitness of the Python executable or the DLLs that it calls*" - what about the Windows side? If `win32` appears only for historical reasons, I would still call this misleading to people seeing this the first time? I mean, Windows is not limited to 32bit addresses anymore – FObersteiner Jan 04 '20 at 10:58

0 Answers0