From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] sage status
Date: Mon, 26 Apr 2010 07:23:16 +0200 [thread overview]
Message-ID: <201004260723.16392.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <4BD4CEC8.7020300@gmx.de>
Hi,
On Monday 26 April 2010 01:22:48 Thomas Kahle wrote:
> Hi,
>
> > * for those of you living on ~arch and are getting headaches because
> > you cannot update python to version 2.6.5, I have committed a patched
> > python-2.6.5 to the overlay. This is not supported by the sage devs so
> > there may be problems.
>
> For those of us living in x86, is it save to use python-2.6.4-r99 as the
> system python??
> I'm slightly worried to use a sage-patched python on global scale...
>
> Regards,
> Thomas
that is a good point - we are also not happy to ship our own python, but
unfortunately a lot of Sage functions are not working without it, as you
already may know.
The difference to the non -r99 version is only a small patch, which is waiting
to be integrated into python (see http://bugs.python.org/issue7689 for an
exhaustive description and patch). I see no reason why this patch should not
be safe - its adding new functionality and does not break existing code. I am
using python-2.6.4-r99 since we were introducing it and did not notice any
problems.
We are hoping that the python people integrate this as soon as possible, but
if you are looking at the bug report date you can see that it already is 3 1/2
months old - does anybody know how to speed up the process ?
Christopher
next prev parent reply other threads:[~2010-04-26 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 7:53 [gentoo-science] sage status François Bissey
2010-04-25 23:22 ` Thomas Kahle
2010-04-26 5:23 ` Christopher Schwan [this message]
2010-04-26 5:32 ` François Bissey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004260723.16392.cschwan@students.uni-mainz.de \
--to=cschwan@students.uni-mainz.de \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox