New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pylibkriging import fails on Windows #103
Comments
Is numpy version OK ? >=1.20 |
Python 3.7 + Windows : OK
|
NB: when it fails because sub-DLL is missing, the error is Moreover, using Dependencies, we can see minor differences between
|
See also #86. |
Yes, for all configurations:
|
Seems to be a common issue between Python 3.7 and 3.8 |
(cf https://stackoverflow.com/a/62891703/12430075)
|
Python ≥3.8 on Windows does not load DLL from path but using os.add_dll_directory()
* Fix python binding. It solves issues: #109, #103 and #86. * Pybind11, carma and armadillo dependencies have updated or upgraded. * Build chain has also been upgraded to follow evolutions of theses libs. * A dedicated memory allocator is now defined in libKriging to drive memory management in armadillo, mostly when linked to Python.
on: Python 3.9.5
But
The text was updated successfully, but these errors were encountered: