Hi Travis,
On 2017-07-25, Travis Scrimshaw wrote:
> There is no discussion about why separate packages: only suggestions about
> doing it without mentioning any of the advantages or disadvantages. Yes, my
> wording is (heavily) loaded, but I did give an advantage to developing a
> separate pac
I have moved to new VPS server, and compilation were done successfully,
same OS ( Ubuntu 16.04.2 LTS (GNU/Linux 2.6.32-042stab120.20 x86_64)) but
with *3.5 GB of RAM. *
*Thanks for the help!!!*
On Friday, July 21, 2017 at 12:03:07 AM UTC-7, Clement Pernet wrote:
>
> Le 19/07/2017 à 22:32, Franç
On 25 Jul 2017 21:16, "Jeroen Demeyer" wrote:
>
> Hello sage-devel and sage-packaging,
>
> I propose to upgrade the PARI package to the git master version instead
of the current released version.
>
>
> A second motivation is that stable releases of PARI are very slow. The
most recent stable PARI r
I know you already signalled in the post but my only answer is
AGAIN!!??
Nevertheless I don’t see that as a biggy anymore because most of the
dependencies of pari (in Gentoo or sage-on-gentoo) happen to be sage
dependencies as well - apart from 2 that are desperately stuck at pari 2.3,
there is
I just created two tickets:
- https://trac.sagemath.org/ticket/23543 for upgrading to the latest
official bugfix release
- https://trac.sagemath.org/ticket/23544 for upgrading to git master
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsu
On 2017-07-25 22:28, William Stein wrote:
+1 -- there were a lot of people at Sage Days last week asking about
feasibility of making a Pari-master package,
since pari stable is so old, and they really needed things in the newers
version of Pari.
Interesting. Do you happen to know which features
On 2017-07-25 22:34, Ximin Luo wrote:
Do you think it would be feasible for Sage "standard" to maintain compatibility
with both PARI stable and the development version?
I have not actually tried, so it is hard to tell right now.
Given the past history of the PARI package inside Sage, I expect
On Tue, Jul 25, 2017 at 1:16 PM Jeroen Demeyer
wrote:
> Hello sage-devel and sage-packaging,
>
> I propose to upgrade the PARI package to the git master version instead
> of the current released version.
>
> The main motivation for me is to use the new plotting engine for the
> PARI Jupyter kerne
Hello sage-devel and sage-packaging,
I propose to upgrade the PARI package to the git master version instead
of the current released version.
The main motivation for me is to use the new plotting engine for the
PARI Jupyter kernel. The plotting engine has changed a lot since the
stable relea
I opened
https://trac.sagemath.org/ticket/23540
On 25/07/2017 11:42, Eric Gourgoulhon wrote:
Le mardi 25 juillet 2017 10:26:54 UTC+2, vdelecroix a écrit :
I think the bug appears when I install pyopenssl. Can somebody else
check whether the following shows the warning?
$ sage -pip install py
@ Marc and William : thanks for the provided information ... I am not
interested with darmonpoints either, and I agree : it will be more useful
to improve the sagemath template project. For making sagedays projects,
public, I think it is interesting matter too ...for "examples" about to use
the
Hi Travis,
Le mardi 25 juillet 2017 08:43:47 UTC+2, Travis Scrimshaw a écrit :
>
> SageManifolds has now been fully integrated into Sage proper, so it
> probably should not be on the list.
>
I've just removed it ;-)
Regards,
Eric.
--
You received this message because you are subscribed to
Le mardi 25 juillet 2017 10:26:54 UTC+2, vdelecroix a écrit :
>
> I think the bug appears when I install pyopenssl. Can somebody else
> check whether the following shows the warning?
>
> $ sage -pip install pyopenssl
> $ sage -q
> sage: quit
> $
>
>
I confirm.
> The above can be reverted
You are making several assertions
1) Sage source code is of good quality
2) We do not test "external packages"
3) Adding and maintaining source code in Sage is simple
Let me discuss them in order.
In my opinion, the most powerful part of Sage comes from its third party
libraries (such as NTL,
Thank you for the reply William!
Rob
--
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
I think the bug appears when I install pyopenssl. Can somebody else
check whether the following shows the warning?
$ sage -pip install pyopenssl
$ sage -q
sage: quit
$
The above can be reverted with
$ sage -pip uninstall pyopenssl
On 24/07/2017 21:46, Eric Gourgoulhon wrote:
Hi Vincent,
I'v
Am Mittwoch, 14. Dezember 2016 20:19:04 UTC+1 schrieb Erik Bray:
>>> Please give this new build a try:
> >>>
> https://github.com/embray/sage-windows/releases/download/0.1a3-7.4/SageMath-7.4.exe
>
>
Will there be a Windows installer for SageMath-8.0?
Peter
--
You received this message bec
Hi,
congrats for Sage 8 release..
I have been interested on Windows native distribution of Sage and I vaguely
remember "reading somewhere a while ago" that Sage 8.0 will possibly have
it..
I can't see on download Sage 8 native Windows release only VM base..
so question is:
is delayed? or was ne
18 matches
Mail list logo
