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

Update setuptools to a newer version #11363

Closed
kiwifb opened this issue May 20, 2011 · 28 comments
Closed

Update setuptools to a newer version #11363

kiwifb opened this issue May 20, 2011 · 28 comments

Comments

@kiwifb
Copy link
Member

kiwifb commented May 20, 2011

For #9958 we will need a newer version of setuptools. Early testing indicate that twisted cannot be installed with the currently shipped version of setuptools and python-2.7.1.

Apply: http://www.d.umn.edu/~strogdon/sage/setuptools-0.6.16.spkg

When this ticket is closed, ticket #10361 can also be closed.

Component: packages: standard

Author: François Bissey

Reviewer: Mariah Lenox

Merged: sage-4.7.1.alpha3

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

@kiwifb kiwifb added this to the sage-4.7.1 milestone May 20, 2011
@kiwifb

This comment has been minimized.

@kiwifb
Copy link
Member Author

kiwifb commented May 21, 2011

Attachment: setuptools-update.patch.gz

update patch, for reviewer only

@kcrisman
Copy link
Member

comment:3

I don't know if this matters, but I get

patching file setup.py
Hunk #1 succeeded at 137 with fuzz 2 (offset 111 lines).

else it installs fine for me.

@kiwifb
Copy link
Member Author

kiwifb commented May 23, 2011

comment:4

I can remove the fuzz but I am not worried by it. I consider a normal part of the patch "aging process" but the ability of fuzz make them a bit more robust and durable than just copying files. But I guess you shouldn't have fuzz for a patch introduced to sage for the first time. I lifted it from Gentoo where it was introduced in an earlier version.

@kiwifb

This comment has been minimized.

@kiwifb
Copy link
Member Author

kiwifb commented May 25, 2011

comment:5

Fuzz removed in ".p0" I had to give it a distinct name because google-code doesn't let delete or replace the old one. It should really be just 0.6.16

@kiwifb
Copy link
Member Author

kiwifb commented May 25, 2011

Author: François Bissey

@sagetrac-mariah
Copy link
Mannequin

sagetrac-mariah mannequin commented May 26, 2011

comment:6

http://spkg-upload.googlecode.com/files/setuptools-0.6.16.p0.spkg unpacks to setuptools-0.6.16 when it should unpack to setuptools-0.6.16.p0.

@kiwifb
Copy link
Member Author

kiwifb commented May 26, 2011

comment:7

Replying to @sagetrac-mariah:

http://spkg-upload.googlecode.com/files/setuptools-0.6.16.p0.spkg unpacks to setuptools-0.6.16 when it should unpack to setuptools-0.6.16.p0.

Working on that. It shouldn't have been named .p0 in the first place, I have to find another place to host the spkg otherwise I'll to name it .p1.

@kiwifb
Copy link
Member Author

kiwifb commented May 26, 2011

comment:8

OK I have it hosted with the right name by my friend Steve now.

@kiwifb

This comment has been minimized.

@sagetrac-mariah
Copy link
Mannequin

sagetrac-mariah mannequin commented May 27, 2011

comment:9

Built sage-4.7.rc4 with setuptools-0.6.16.spkg with 'make testlong'. All tests passed. Positive review!

@sagetrac-mariah
Copy link
Mannequin

sagetrac-mariah mannequin commented May 27, 2011

Reviewer: Mariah Lenox

@sagetrac-Koen
Copy link
Mannequin

sagetrac-Koen mannequin commented May 30, 2011

comment:10

As soon as this ticket is fixed, then Ticket #10361 can also be closed (as this ticket supersedes that one by upgrading to an even newer setuptools, and fixing the Twisted/OSX issue).

@kiwifb
Copy link
Member Author

kiwifb commented May 30, 2011

comment:11

Pity I didn't see that ticket. May be I would have reviewed it instead.

@sagetrac-mariah

This comment has been minimized.

@jhpalmieri
Copy link
Member

comment:13

As far as I can tell, the spkg here is not really setuptools, but a fork of it called "distribute". At least, I can't find setuptools 0.6.16 on the setuptools web page http://pypi.python.org/pypi/setuptools, but I do see it on the distribute page http://pypi.python.org/pypi/distribute. This needs to be documented in the SPKG.txt file: update both the description and the web page.

On the bright side, on my OS X box at least, it doesn't seem to suffer from the same problem as reported on #10361.

@kiwifb
Copy link
Member Author

kiwifb commented May 31, 2011

comment:14

Right. I should have paid more attention you are right. I will update SPKG.txt with the needed info. I will post again when it is available so you can decide if it can be switched back to positive review.

@kiwifb
Copy link
Member Author

kiwifb commented May 31, 2011

Attachment: SPKG.txt.patch.gz

Latest changes to SPKG.txt for the reviewer only

@kiwifb
Copy link
Member Author

kiwifb commented May 31, 2011

comment:15

New spkg uploaded at the same location. I attached a patch which details my latest change to SPKG.txt.

@jdemeyer
Copy link

Merged: sage-4.7.1.alpha3

@jhpalmieri
Copy link
Member

comment:18

Ticket #7230 can also be closed because of this.

@nexttime
Copy link
Mannequin

nexttime mannequin commented Jun 24, 2011

comment:19

I think it's not a bad idea to look at previous tickets dealing with an spkg when updating it.

In this case #10361 (updating setuptools to 0.6c11), which got positively reviewed and merged, but later unmerged again due to an issue with twisted on MacOS X.

The changes made there, namely

  • making spkg-install executable,
  • adding a Special Update / Build Instructions section to SPKG.txt (with a note on deleting the Windows binaries),
  • removing mabs from the spkg maintainer list (I'm not sure if that's still desired),
  • substituting #!/bin/sh by #!/usr/bin/env bash, and, last but not least
  • adding error checks to spkg-install (though now in addition patches are applied from it)
    are all missing in the new spkg here.

Btw, the patch attachment: setuptools-update.patch (for review purposes) doesn't really reflect the changes made to (Sage's part of) the spkg, which is perhaps minor here, but still a bit confusing.

@kiwifb
Copy link
Member Author

kiwifb commented Jun 24, 2011

comment:20

You are quite right leif and I probably could have done a better job. My only defense is I absolutely hate searching on trac. It takes ages and most of the results are not that relevant. I get better results from Gentoo's bugzilla - although it is sometimes quite slow at least I usually got interesting results.

I am not sure I understand your last comment. The posted patch summarizes the changes to the spkg and is not meant to be applied, just to give you a quick look at the changes. It seems to be a common enough practice.

@nexttime
Copy link
Mannequin

nexttime mannequin commented Jun 24, 2011

comment:21

Replying to @kiwifb:

You are quite right leif and I probably could have done a better job.

Well, there are reviewers, too, and in fact some people who commented here were aware of that ticket.

My only defense is I absolutely hate searching on trac. It takes ages and most of the results are not that relevant.

Yes, especially if you're searching for things like R... 8-)

I am not sure I understand your last comment. The posted patch summarizes the changes to the spkg and is not meant to be applied, just to give you a quick look at the changes. It seems to be a common enough practice.

Not really relevant here, but even patches / diffs just for reference should IMHO be up-to-date. I just stumbled upon

--- setup.py    2007-09-04 19:18:46.000000000 +0300 
+++ setup.py    2007-11-04 09:49:18.000000000 +0200 
@@ -26,7 +26,6 @@ 
     url = "http://pypi.python.org/pypi/setuptools", 
     test_suite = 'setuptools.tests', 
     packages = find_packages(), 
-    package_data = {'setuptools':['*.exe']}, 
  
     py_modules = ['pkg_resources', 'easy_install', 'site'], 

which definitely belongs to an earlier version of the spkg. (Note the url in the context.)

If someone is lazy (like me), he might review (more or less) just the spkg diff on trac as is, assuming it reflects the current state of the spkg, such that mistakes or unintended changes made later may sneak in.

@nexttime
Copy link
Mannequin

nexttime mannequin commented Jun 24, 2011

comment:22

P.S.: I usually cc the spkg maintainers (as listed in SPKG.txt, and also on a completely outdated wiki page ;-) ), though apparently these entries have lost meaning, unfortunately.

@nexttime
Copy link
Mannequin

nexttime mannequin commented Jun 24, 2011

comment:23

P.P.S.: You can also search (with G**gle) http://groups.google.com/group/sage-trac, which even gives suitable results for "R".

That's IMHO the only useful aspect of this group; I don't like feeding G**gle with all that stuff otherwise.

@kiwifb
Copy link
Member Author

kiwifb commented Jun 24, 2011

comment:24

Replying to @nexttime:

P.P.S.: You can also search (with G**gle) http://groups.google.com/group/sage-trac, which even gives suitable results for "R".

That's IMHO the only useful aspect of this group; I don't like feeding G**gle with all that stuff otherwise.

Possibly the best idea since sliced bread! Thanks a lot for pointing it out. And yes I have been treating maintainers like they do not exist (apart David Kirkby but we seem to end up doing a lot of things together so this may explain that) which is of course terribly impolite of me.

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