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
[GCC10] Fix scipy and sckikit-learn for gcc10 #5842
Conversation
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
the py2 version is unchanged, it only adds a fortran flag to deal with the new defaults in gcc10. |
Ah - I think we didn’t consider the gcc support aspect of the end of python2 support issue.. Interesting..
Does the same flag solve the errors on scipy 1.4.1 as with 1.2.3? Perhaps we should live with that change rather than picking up an unreleased version of scipy? I don’t have a strong opinion, is just a thought.
On May 22, 2020, at 11:51 AM, Mircho Rodozov <notifications@github.com<mailto:notifications@github.com>> wrote:
the py2 version is unchanged, it only adds a fortran flag to deal with the new defaults in gcc10.
the change for py3 comes from here:
scipy/scipy#11842<scipy/scipy#11842>
which is above 1.4.1 and not an official release. The question is - is that ok ?
I tried to backport the same change for py2 but 1.2.3 is so much different/older than 1.4.x that this backport became too much of an effort and had to leave it.
Many python packages are having either no support for py2 since given version or some support that comes from old releases, like this one, which becomes a serious problem when one have to deal with the fortran part.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub<#5842 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGPFQ3N3LE23JWOOHY6P6DRSZDK3ANCNFSM4NHLEATQ>.
|
I didn't think of this because the py3 solution is surgical and the py2 one is not: adds a flag globally to everything, but now it doesn't sound so bad ... |
adds the flag and the pkg is building
please test |
The tests are being triggered in jenkins. |
Pull request #5842 was updated. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_11_2_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
please test