BUG: detect buggy windows version and raise at import

[mattip]

xref gh-16744. Use a check at import to make sure we are not sensitive to the fmod bug in windows. Alternative to gh-17547.

@bashtage could you check if these PRs works as advertised?

[bashtage]

Does what it says.

In [1]: import numpy as np
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-1-0aa0b027fcb6> in <module>
----> 1 import numpy as np

c:\anaconda\envs\python-pip\lib\site-packages\numpy\__init__.py in <module>
    374
    375     if sys.platform == "win32" and sys.maxsize > 2**32:
--> 376         _win_os_check()
    377
    378     del _mac_os_check

c:\anaconda\envs\python-pip\lib\site-packages\numpy\__init__.py in _win_os_check()
    371                    "See this issue for more information "
    372                    "https://developercommunity.visualstudio.com/content/problem/1208774/fpu-exception-in-fmod0-x-in-windows-10-version-200.html")
--> 373             raise RuntimeError(msg.format(__file__)) from None
    374
    375     if sys.platform == "win32" and sys.maxsize > 2**32:

RuntimeError: The current Numpy installation ('c:\\anaconda\\envs\\python-pip\\lib\\site-packages\\numpy\\__init__.py') fails to pass a sanity check due to a bug in the windows runtime. See this issue for more information https://developercommunity.visualstudio.com/content/problem/1208774/fpu-exception-in-fmod0-x-in-windows-10-version-200.html

[bashtage]

Maybe you need to make the exception more explicit?

[mattip]

@bashtage if you could try it again that would be great. There were various typos and mistakes in the original version.

[bashtage]

@mattip Still does the job.

[pv]

Maybe this is OK to merge, even if also gh-17547 gets in? Import-time sanity check probably can't hurt, in case similar bug gets reintroduced in another Windows update.

[mattip]

Since OpenBLAS 0.3.12 avoids using the messed-up registers, this check is no longer relevant. Closing.

[charris]

I think there are some hard tabs in here.

[charris]

2004, not 200?

[bashtage]

The URL is correct, despite missing the 4.

[charris]

NVM.

[charris]

I used "https://tinyurl.com/y3dm3h86" instead.

[wonkodv]

Hi, I came here from a pip installation that is refusing to work now, looking for a workaround, but did not find anything.

Am I correct in saying, that this is not a problme on 32 bit python?

If so, I would ask you to change the error message so that it links to this wiki page I just made instead of to the visual studio bugtracker.

https://github.com/numpy/numpy/wiki/FMod-Bug-on-Windows

[bashtage]

You are correct that there is no issue on 32 but windows. The best workarounds are to either use WSL or 32 bit. Neither has the fmod bug.