#9958: Upgrade python to 2.7
---------------------------+------------------------------------------------
Reporter: mhampton | Owner: tbd
Type: enhancement | Status: needs_work
Priority: major | Milestone:
Component: packages | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies: #11156 #11236 #11244 #11264
#11339 #11363 #11376
---------------------------+------------------------------------------------
Comment(by leif):
Just for the record:
http://trac.sagemath.org/sage_trac/ticket/8664#comment:33 gives an example
on how to automatically rebuild packages that depend on a newly added spkg
(here: Python).
(Artificial version bumps aren't necessary, and simply `touch`ing
`spkg/installed/<spkg-that-others-depend-on>` alone doesn't work.)
In general:
1. Copy the new spkg(s) to `$SAGE_ROOT/spkg/standard/`.
1. `export SAGE_UPGRADING=yes`
1. (Optionally set `MAKE` and `SAGE_PARALLEL_SPKG_BUILD`, perhaps
`SAGE_CHECK`.)
1. Run `make` (or better `make build`) rather than doing `./sage -f ...`
1. Apply patches to the Sage library.
1. Run `./sage -b` (or `./sage -ba-force` in case not all dependencies
are covered by `module_list.py`, which in general I'd consider a bug, but
this might be necessary upon a Python upgrade)
1. Run tests or whatever.
Note that Sage switches to the "main" branch whenever the Sage spkg gets
reinstalled.
Of course patches to the build system are usually a bit trickier, but as
far as I can see Francois already sorted these out.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9958#comment:73>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
