Opened 11 years ago
Closed 11 years ago
#70 closed task (fixed)
python: Update to 2.7
Reported by: | dmik | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | python | Version: | |
Severity: | Keywords: | ||
Cc: |
Description
This ticket is to track Python updates from 2.6 to 2.7.
Attachments (1)
Change History (8)
comment:1 by , 11 years ago
by , 11 years ago
Attachment: | paul-2.7.5.diff added |
---|
comment:2 by , 11 years ago
Paul, I handled Python-2.7.5.diff
that you sent to me some time earlier. Most of the patches from there are of course already in this repo (as both are based on your earlier work). Those that are new and make sense to me I committed here giving you credit (please check the timeline).
Some new patches are not fully clear to me: I attached them to this ticket as paul-2.7.5.diff. Please review and tell what every change is intended for — to make it clear what it fixes.
The rest was not applied since it's either spacing/indentation, missing debug statements or repeats of what I already did (in either exactly the same or a slightly different way). Please check it all out and tell me if you are satisfied with the current state.
I also repeat the request to base all your further python work on this repository — to make sure nothing is lost and no work is duplicated. Just attach your future patches to a ticket and I (or Yuri) will apply them here. I'm also ready to help you with the vendor update stuff here.
comment:3 by , 11 years ago
pthread stuff is from some experimentation I did converting from os2 api to pthreads to see if it helped with a particular problem I was working on at the time.
I don't recall the reasons for the rand stuff.
I most likely won't release any further builds of 2.7.x - there are unlikely to be future upstream releases
comment:4 by , 11 years ago
So, did switching to OS/2 threading API helped you with that problem?
And what about /ctypes/init.py? Do you remember where/when is it used?
Regarding further builds of Python. This relates not only to 2.x but to 3.x as well of course as 3.x is still derived from 2.x I guess (and hence most our patches from this SVN will be still applicable).
Forgot to mention that I also dropped your patches where you hardcode your specific paths (like /extras/include
) and build options. Options and paths are specified at the RPM .spec level here (which acts much like a build script that everybody may use even if they don't actually want to provide an RPM), so they should not be hardcoded in SVN. If you still want to have them, we may simply create a branch named psmedley
here and you can keep all your patches there. I can also help you with this branch. And we may give you commit access I'm sure (so that you could work on your branch on your own) - this would be even better than attaching patches to tickets.
comment:5 by , 11 years ago
No,no difference between pthreads and os2 pthread with the problem I was working on. IIRC the ctypes/init.py was also related to using pthreads/dlopen in lieu of os2 apiss
comment:6 by , 11 years ago
Okay, then I will not apply these two remaining patches for the time being.
comment:7 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The 2.7 packages are ready and in the repository. There is some issue with compatibility, see #71 for details.
I've actually updated trunk to 2.7.6.
This ticket is to discuss some remaining bits, in particular some of the Paul's newest 2.7 patches which are not fully clear to me. I will attach them in a moment.