Skip to content
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.15.1 #11761

Closed
robertwb opened this issue Aug 31, 2011 · 36 comments
Closed

Upgrade Cython to 0.15.1 #11761

robertwb opened this issue Aug 31, 2011 · 36 comments

Comments

@robertwb
Copy link
Contributor

Lots of improvements and bug fixes, including generators.

See http://wiki.cython.org/ReleaseNotes-0.15.1 for details.


New spkg: http://sage.math.washington.edu/home/jdemeyer/spkg/cython-0.15.1.spkg

Apply attachment: 11761-cython-0.15-rebased.patch and attachment: 11761_review.patch to the Sage library.

CC: @kiwifb @jpflori

Component: packages: standard

Author: Robert Bradshaw

Reviewer: Jeroen Demeyer

Merged: sage-4.8.alpha1

Issue created by migration from https://trac.sagemath.org/ticket/11761

@nexttime
Copy link
Mannequin

nexttime mannequin commented Aug 31, 2011

Replying to @robertwb:

... including generators.

Yeah!

@robertwb
Copy link
Contributor Author

@robertwb
Copy link
Contributor Author

comment:5

Note that 0.15.1 is around the corner, but it's not as big of a jump.

@nexttime
Copy link
Mannequin

nexttime mannequin commented Sep 16, 2011

Author: Robert Bradshaw

@nexttime

This comment has been minimized.

@nexttime
Copy link
Mannequin

nexttime mannequin commented Sep 16, 2011

comment:6

Would 0.15.1 require additional changes to Sage?

@jasongrout
Copy link
Member

comment:7

Just FYI, 0.15.1 is now released.

@nexttime
Copy link
Mannequin

nexttime mannequin commented Oct 2, 2011

comment:8

Replying to @jasongrout:

Just FYI, 0.15.1 is now released.

Oh, did you tell Robert?

(Although he said "it's not as big of a jump".)

@jasongrout
Copy link
Member

comment:9

Replying to @nexttime:

Replying to @jasongrout:

Just FYI, 0.15.1 is now released.

Oh, did you tell Robert?

Oh, I'm sure he knows, since he's the BFDL for Cython, if there is such a position ;).

(Although he said "it's not as big of a jump".)

@nexttime
Copy link
Mannequin

nexttime mannequin commented Oct 2, 2011

comment:10

Replying to @jasongrout:

Replying to @nexttime:

Replying to @jasongrout:

Just FYI, 0.15.1 is now released.

Oh, did you tell Robert?

Oh, I'm sure he knows, since he's the BFDL for Cython, if there is such a position ;).

I was just kidding.

(Wonder whether he updates the spkg... :P)

@nexttime
Copy link
Mannequin

nexttime mannequin commented Oct 2, 2011

comment:11

:)

@nexttime nexttime mannequin changed the title Upgrade Cython to 0.15 Upgrade Cython to 0.15 or later Oct 2, 2011
@robertwb

This comment has been minimized.

@robertwb
Copy link
Contributor Author

robertwb commented Oct 4, 2011

comment:12

No further patches needed for 0.15.1.

@robertwb robertwb changed the title Upgrade Cython to 0.15 or later Upgrade Cython to 0.15.1 Oct 4, 2011
@jdemeyer
Copy link

Attachment: 11761-cython-0.15-rebased.patch.gz

@jdemeyer

This comment has been minimized.

@jdemeyer jdemeyer modified the milestones: sage-4.7.2, sage-4.8 Oct 31, 2011
@jdemeyer
Copy link

Attachment: cython-0.15.1.diff.gz

Diff for the new Cython spkg, for review only

@jdemeyer
Copy link

comment:14

Minor comment: spkg-install is not executable (I know it is made executable upon building, but better fix this in the spkg anyway).

@jdemeyer

This comment has been minimized.

@jdemeyer
Copy link

comment:16

Why is the directory tests missing from the Cython source? This should either be fixed, or be documented.

@jdemeyer
Copy link

comment:19

This new Cython really gives a lot more warnings than the old one, in many cases for code which is perfectly fine. For me, this isn't really a problem, but it is certainly annoying.

@robertwb
Copy link
Contributor Author

robertwb commented Nov 1, 2011

comment:20

I've fixed the executable bit on spkg-install and added the tests to the spkg. (I remember someone complaining way back that they were too big, but I don't think it's an issue and we've regularly shipped them before, and it's easier to just have them there.) The spkg at the above link has been refreshed.

The warnings are primarily due to the fact that mpz_t et al are declared as void* rather than arrays of size 1. http://hg.sagemath.org/sage-main/file/2a2abbcad325/sage/libs/gmp/types.pxd#l1 Once this is fixed the warnings should go away (and they are correct with respect to the current declarations). All the other warnings I've noticed are correct too, I simply haven't had the time to fix/update Sage's code.

Your review patch looks fine. You obviously looked at this, is the window closed for 4.7.2?

@jdemeyer
Copy link

jdemeyer commented Nov 1, 2011

comment:21

Replying to @robertwb:

Your review patch looks fine.

In fact, it doesn't. I removed one line too much, fixed now.

You obviously looked at this, is the window closed for 4.7.2?

This will certainly not be merged in sage-4.7.2.

@jdemeyer
Copy link

jdemeyer commented Nov 1, 2011

comment:22

Attachment: 11761_review.patch.gz

Replying to @robertwb:

The warnings are primarily due to the fact that mpz_t et al are declared as void* rather than arrays of size 1. http://hg.sagemath.org/sage-main/file/2a2abbcad325/sage/libs/gmp/types.pxd#l1 Once this is fixed the warnings should go away (and they are correct with respect to the current declarations).

If there is an easy way to fix this, then we should do this. I'm saying we should fix every single warning but if it is possible to declare mpz_t such that there are no warnings, we should certainly do this.

@jdemeyer
Copy link

jdemeyer commented Nov 1, 2011

comment:23

Of course, that should have been "I'm not saying we should fix every single warning"

@jdemeyer
Copy link

jdemeyer commented Nov 1, 2011

comment:24

Replying to @robertwb:

I've fixed the executable bit on spkg-install and added the tests to the spkg.

One more thing: changing permissions is a change which should be committed. So could you please do a hg commit and re-upload the spkg? Otherwise, the package and patch looks good.

@jdemeyer
Copy link

jdemeyer commented Nov 3, 2011

Milestone sage-4.7.3 deleted

@jdemeyer jdemeyer removed this from the sage-4.8 milestone Nov 3, 2011
@robertwb
Copy link
Contributor Author

robertwb commented Nov 5, 2011

comment:26

Spkg updated with executable bit set commit.

@robertwb robertwb added this to the sage-4.8 milestone Nov 5, 2011
@robertwb
Copy link
Contributor Author

robertwb commented Nov 5, 2011

comment:27

Yes, I agree these warnings should be fixed. #11992 .

@jdemeyer
Copy link

jdemeyer commented Nov 5, 2011

comment:28

Replying to @robertwb:

Spkg updated with executable bit set commit.

Looks you forgot to update the spkg, it is exactly the same as before (last modified on 1 november):

$ ls -l /home/robertwb/cython/spkg/cython-0.15.1.spkg
-rw-r--r-- 1 robertwb robertwb 1420704 2011-11-01 06:57 /home/robertwb/cython/spkg/cython-0.15.1.spkg

Never mind, I will make the change.

@jdemeyer

This comment has been minimized.

@robertwb
Copy link
Contributor Author

robertwb commented Nov 5, 2011

comment:30

Oops, I put it at

robertwb@sage:~/cython$ ls -l /home/robertwb/cython/cython-0.15.1.spkg 
-rw-r--r-- 1 robertwb robertwb 1412114 2011-11-04 22:51 /home/robertwb/cython/cython-0.15.1.spkg

That's what comes of getting too little sleep. Go ahead and use that one (or if you've already done the trivial change, even better.)

@jdemeyer
Copy link

jdemeyer commented Nov 7, 2011

Merged: sage-4.8.alpha1

@kiwifb
Copy link
Member

kiwifb commented Nov 24, 2011

comment:32

Sorry to be late to the party. I get an error building the optional mpc extension in 4.8.alpha2 and I suspect cython-0.15.1 is the problem

sage/rings/complex_mpc.c: In function '__pyx_pf_4sage_5rings_11complex_mpc_15MPComplexNumber_16__float__':
sage/rings/complex_mpc.c:9720:48: error: cast specifies array type

I am guessing the complex_mpc.pyx code needs to be updated but I don't really know how.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants