#11376: Remove the hardcoding of python version in setup.py and SConstruct to
build
sage_clib and sage itself
---------------------------+------------------------------------------------
Reporter: fbissey | Owner: GeorgSWeber
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.7.1
Component: build | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author: François Bissey
Merged: | Dependencies:
---------------------------+------------------------------------------------
Old description:
> Currently to build sage (the spkg) four files are involved in major way:
> 1. SConstuct to build sage-clib
> 1. setup.py
> 1. module_list.py
> 1. sage/misc/cython.py
>
> The last three to build the sage python extensions. setup.py, and
> SConstruct both have the version of python used hardcoded in them,
> module_list.py doesn't refer to the python version anywhere. cython.py
> mention the python version explicitly in doctest but smartly find the
> version used for building all by itself.
>
> In this ticket I bring this smartness to SConstruct and setup.py. The
> advantage of doing this is that sage then can be build with either
> python-2.6 or 2.7 (and 3.x in the future) without patching. Of course it
> may still require patches to fix doctest and syntax in some parts - but
> you would be able to build sage in the first place without having to
> patch the build system. It has been found to be an impediment to testing
> in #9958.
New description:
Currently to build sage (the spkg) four files are involved in major way:
1. SConstuct to build sage-clib
1. setup.py
1. module_list.py
1. sage/misc/cython.py
The last three to build the sage python extensions. setup.py, and
SConstruct both have the version of python used hardcoded in them,
module_list.py doesn't refer to the python version anywhere. cython.py
mention the python version explicitly in doctest but smartly find the
version used for building all by itself.
In this ticket I bring this smartness to SConstruct and setup.py. The
advantage of doing this is that sage then can be build with either
python-2.6 or 2.7 (and 3.x in the future) without patching. Of course it
may still require patches to fix doctest and syntax in some parts - but
you would be able to build sage in the first place without having to patch
the build system. It has been found to be an impediment to testing in
#9958.
Depend: #11373
Apply:
* [attachment:trac_11376-build-sage_clib.patch]
* [attachment:trac_11376-build_setuppy.patch]
--
Comment(by fbissey):
Decided to avoid problem with #11373 so make it depend on it.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11376#comment:11>
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.
