Dave, On Mar 30, 3:21 am, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: [...] > What I do find odd is to make > Python a prerequisite, then also include the python sources too. That > means people are going to need to have two copies of python.
most likely, two different versions. E.g. Debian stable does not have Python 2.6, at all. It is in Debian testing, but not as a default Python. (Most of Linux systems out there have a bunch of different versions of Python installed, IMHO) Cygwin does not have Python 2.6 at present, either. > I would > imagine such a strategy would be even more difficult to "sell" to > groups like Debian for the perposes of packaging. One could argue a > requirement to ship python sources, but it gets even more difficult to > argue that python is a prerequisite, but we still ship the sources. > Personally I would think that anything that needs to be done before > python is built should be done in bash scripts. really, "some" Python 2.5 or 2.4 or 2.6 is quite easy to get for any system Sage supports or intends to support. Getting exactly the same Python as Sage runs on is quite different story, and can be hard. The only alternative would be to make Sage running on the zillon Pythons 2.x.y , for each x.y>x0.y0, out there, and this seems infeasible. Dima > Of course, there is > nothing stopping python being built very early on. > > Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
