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
MAINT: fix libquadmath licence #19299
Conversation
|
||
|
||
Name: libquadmath | ||
Files: scipy.libs\libopenblas*.dll |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of the PR looks similar to what Matti/Ralf did upstream, and so does this, but this looks incorrect because it is quadmath with OpenBLAS shared lib, and also if we statically linked I'm not sure it would be a dll vs. i.e., .a
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess that is indeed what is in the distributed wheel, so maybe it is just the line about static linking below that confuses me re: DLL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed in numpy/numpy#24793.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @andyfaff. And yes, +1 for backporting.
Waiting for a bit with merging to see if there are any more comments on this PR or the numpy one.
I still think that, from a license consumption standpoint, if you statically link i.e., libquadmath to OpenBLAS, and then dynamically load openblas, you're ultimately a runtime dynamic link consumer of the binary asset, but I'm happy to consider myself outvoted 2-1 here. Also, because Ralf's upstream analysis was that the distinction was apparently irrelevant from the standpoint of the quadmath license anyway, so spending energy on this would be doubly pointless: numpy/numpy#24793 (comment) |
* MAINT: linux amendments * MAINT: osx amendments * MAINT: win licence amendments * MAINT: licence typo
See https://github.com/numpy/numpy/pull/24785/files and MacPython/openblas-libs#114 for relevance.
I think these should be backported to all active maintenance branches.