2015-02-18 17:06 UTC+01:00, Jeroen Demeyer <jdeme...@cage.ugent.be>:
> On 2015-02-18 16:46, Julien Puydt wrote:
>> Le 18/02/2015 15:57, Jeroen Demeyer a écrit :
>>> On 2015-02-18 15:51, Julien Puydt wrote:
>>>> Is pari's output changing that often, that failing doctests could have
>>>> so little meaning?
>>> Yes.
>>
>> Then perhaps it's a good idea to replace those two results (32-bit and
>> 64-bit) by a single "tol" one?
>
> It could be done, but it doesn't solve the deeper issue: if
> Sage-on-Debian and vanilla-Sage use different versions of PARI (or other
> packages), you cannot really expect things to work properly...
>
> Personally, I really hope that vanilla-Sage upgrades to PARI-unstable
> (either git master or PARI 2.8.0 whenever that comes out). That's a huge
> change from PARI 2.7.x, what will you do on Debian then?
Julien built an almost working prototype for a native sage on debian.
This implies out of the box installation for a lot of users (and
potentially much cleaner integration of third party softwares). The
real question is:
does the Sage community will officially support sage on debian ?
I really hope that the answer is yes. If it is the case, it is a big
-1 for having PARI-unstable within Sage. Unless of course Bill and
Karim agreed on having an official pari-unstable package in debian.
Vincent
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
