-
Notifications
You must be signed in to change notification settings - Fork 187
Avoid deprecated BLAS.vendor() in MKL conflict check #950
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
Conversation
Patch as suggested by Carsten Bauer in JuliaPy#922. GitHub: Fixes JuliaPy#922.
Co-authored-by: Mosè Giordano <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #950 +/- ##
==========================================
- Coverage 68.33% 68.33% -0.01%
==========================================
Files 20 20
Lines 2018 2021 +3
==========================================
+ Hits 1379 1381 +2
- Misses 639 640 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Can this be merged? |
bump |
Registering: JuliaRegistries/General#55870 |
Thanks! |
Patch as suggested by Carsten Bauer in #922.
As discussed in #922, the new BLAS trampoline magic might allow us to avoid this issue altogether, but this is nontrivial, as it would involve loading MKL in two different configurations even if it did work (the libtrampoline author wasn't sure about that either). For now, this avoids the annoying warning every time PyCall is loaded.