I believe the next releases (1.19.x or 1.20.0, whichever if first) of NumPy should have 0.3.12 built using a smaller buffersize which will make this import error stop appearing on Windows, irrespective of the MS-provided fix. From: Oscar Benjamin The final message in the numpy issue suggests a possible fix: https://github.com/numpy/numpy/issues/16744#issuecomment-727098973 """ My preference would be to have a 1.19.5 that uses OpenBLAS 0.3.9 on Linux and 0.3.12 on Windows, but I don't know if this is possible. """ I don't know if that would fix the problem or how hard that would be to implement but I am seeing an increasing flow of problem reports in different fora about this issue and I'm surprised that the plan is to wait for MS to (possibly) release a fix in two month's time. -- Oscar On Thu, 3 Dec 2020 at 21:14, Alan G. Isaac <alan.is...@gmail.com> wrote: > > "current expectation is that this [fix] will be able to be released near the end of January 2021" > ! > > > On 12/2/2020 7:13 PM, Ilhan Polat wrote: > > Yes this is known and we are waiting MS to roll out a solution for this. Here are more details > > https://developercommunity2.visualstudio.com/t/fmod-after-an-update-to-windows-2004-is-causing-a/1207405 > > <https://developercommunity2.visualstudio.com/t/fmod-after-an-update-to-windows-2004-is-causing-a/1207405> > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion |
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
