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
Upgrade Cython to 0.14.1 #10493
Comments
comment:1
We're in pretty good shape. There's a couple of minor patches to the library that need to go in, but other than that upgrading to 0.14 should be pretty straightforward. See, e.g. https://sage.math.washington.edu:8091/hudson/view/ExtLibs/job/sage-tests/ |
Changed keywords from none to cython spkg |
comment:2
Is the |
comment:3
No, that is now handled via a flag. There are several bugfixes in 0.14.1 that I'd like to get in, which should be out shortly (before 4.6.2 is at release candidate for sure, and I knew we missed the window for 4.6.1) which is why I haven't done anything on this ticket yet. |
comment:4
Updated package with just the |
comment:5
Thanks, but that is not sufficient, as we need to pass the appropriate flags. The most recent spkg can be found at https://sage.math.washington.edu:8091/hudson/job/sage-build/lastSuccessfulBuild/artifact/cython-devel.spkg (though the Sage library requires a couple of patches as well). |
This comment has been minimized.
This comment has been minimized.
comment:6
Updating the description to upgrade to 0.14.1, which is now the most recent release. Has anyone worked on an 0.14.1 spkg? |
comment:7
Attachment: 10493-cython-0.14.1.patch.gz Spkg at http://sage.math.washington.edu/home/robertwb/cython/cython-0.14.1.spkg |
comment:9
Replying to @robertwb:
Is this still the case with the 0.14.1 spkg? |
comment:10
I think that's what the patch is all about. I applied it to 4.6.2.alpha4 and it happily built and sage -testall did not show any problems for me. But may be the following warnings should be addressed
And possibly
Finally I am wondering about these
But all these were present before upgrading to cython-0.14.1. |
comment:11
Forgot these two:
|
comment:12
Yes, the (attached) patch is still needed. There's some significant cleanup that I want to do, including fixing these warnings, but I think that should be a separate ticket. |
comment:13
Well if you open a separate ticket for these warnings I am quite happy to give this a positive review. I have built it on linux-86, linux-amd64 and OS X 10.5. |
This comment has been minimized.
This comment has been minimized.
comment:14
Ticket for warnings at #10764. |
Reviewer: François Bissey |
Author: Robert Bradshaw |
comment:16
After building sage-4.6.2.rc0 and applying the spkg and patch from this ticket:
This is using
|
comment:20
I've created a new spkg. All tests pass. |
This comment has been minimized.
This comment has been minimized.
comment:21
Replying to @robertwb:
How come you and I never got affected by it? |
comment:22
I'm not sure, but maybe the last spkg was the rc, and the fix for this issue was not supposed to go in this release, but we messed up and it did. |
comment:23
It works for me now, so I'm putting back the positive review. |
comment:24
Thanks. |
Merged: sage-4.7.alpha1 |
comment:26
Please fix: the SPKG.txt must be updated, there is no mention of this ticket. |
comment:27
The SPKG.txt has been updated, see http://sage.math.washington.edu/home/robertwb/cython/cython-0.14.1.p2.spkg |
This comment has been minimized.
This comment has been minimized.
comment:28
Attachment: cython-SPKG.txt.diff.gz I made some further changes to SPKG.txt: http://boxen.math.washington.edu/home/jdemeyer/spkg/cython-0.14.1.p3.spkg |
This comment has been minimized.
This comment has been minimized.
comment:29
I'm happy with your spkg.txt. |
Version 0.14.1 was recently released, and has some bugfixes and nice features.
Use the following spkg and patch:
CC: @robertwb @kiwifb
Component: packages: standard
Keywords: cython spkg
Author: Robert Bradshaw
Reviewer: François Bissey
Merged: sage-4.7.alpha1
Issue created by migration from https://trac.sagemath.org/ticket/10493
The text was updated successfully, but these errors were encountered: