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 BenjaminSent: Friday, December 4, 2020 12:05 AMTo: Discussio
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
Hi All,
On behalf of the NumPy team I am pleased to announce the release of NumPy
1.20.0rc1. This NumPy release is the largest to date, containing some 654
merged pull requests contributed by 182 people. See the list of highlights
below. The Python versions supported for this release are 3.7-3.9,
"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-
