-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
python3.pkgs.rpy2: 2.9.5 -> 3.2.2 #74537
Conversation
I would to split out the changes into 2 commits:
|
But python2 rpy2 was already frozen at 2.8.6. The only difference is that previously, both versions were maintained in the same file because 2.9.x (the py3 version) was similar enough. |
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.
this does seem to cause a regression with sage:
builder for '/nix/store/ss4rkx5p5aciz5nidlrzr088y00951br-sage-tests-8.9.drv' failed with exit code 1; last 10 log lines:
sage -t --long /nix/store/62xwy4d6055qshylxl7n63idga66d96b-sage-src-8.9/src/sage/schemes/elliptic_curves/ell_rational_field.py
[847 tests, 132.16 s]
sage -t --long /nix/store/62xwy4d6055qshylxl7n63idga66d96b-sage-src-8.9/src/sage/rings/function_field/function_field.py
[750 tests, 211.04 s]
----------------------------------------------------------------------
sage -t --long /nix/store/62xwy4d6055qshylxl7n63idga66d96b-sage-src-8.9/src/sage/matrix/matrix_space.py # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 652.0 seconds
cpu time: 10508.3 seconds
cumulative wall time: 13614.3 seconds
cannot build derivation '/nix/store/4i6b3xy9yh0frl6zakibjm83wxz7l2iz-sage-8.9.drv': 1 dependencies couldn't be built
@jonringer I cannot reproduce that. Neither on this branch, nor on master. This PR really shouldn't change anything for sage, since sage uses the py2 version which is still pinned on the same version. The full log would be interesting. Is the failure reproducible for you? |
You can run just that one test like this:
|
I was also running a few other reviews, and it looks like it failed on a performance test. Could have been starved for cpu resources. If you feel confident it will pass on hydra, then I'm fine with it |
There have been significant changes, therefore it doesn't make sense anymore to maintain the python2 and python3 version in the same file. We'll be able to drop the python2 version soon, some time after we have switched sage to python3.
Motivation for this change
There have been significant changes, therefore it doesn't make sense
anymore to maintain the python2 and python3 version in the same file.
We'll be able to drop the python2 version soon, some time after we have
switched sage to python3.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @