On Thu, 24 Aug 2017, kcrisman wrote:
OK. What packages or parts have been updated lately?
See perhaps https://trac.sagemath.org/ticket/22431 or
https://trac.sagemath.org/ticket/23066 though I don't see
immediately which packages were upgraded there.
#22431 is a new ticket, but #23066
On Thu, 24 Aug 2017, Dima Pasechnik wrote:
sagenb is installed by pip, which pulls packages from the net; whatever comes up as the
"stable" version,gets
installed. We used to pin down versions, but don't do this any more.
You can look at the output of
./sage --pip list
to see what versions y
Puzzle:Why does it take nearly **twice as long** to just run sage and exit
as it does to import the sage library and run a command?Timings below are
on an SSD:
~$ time sage -python -c "import sage.all; sage.all.factor(2018)"
real
On Thursday, August 24, 2017 at 2:50:09 PM UTC-7, William wrote:
>
> On Thu, Aug 24, 2017 at 2:17 PM, Nils Bruin >
> wrote:
> > On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote:
> >>
> >> I'm not sure what the status is these days, but we may want to stop
> >> including a pyth
On Thu, Aug 24, 2017 at 2:17 PM, Nils Bruin wrote:
> On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote:
>>
>> I'm not sure what the status is these days, but we may want to stop
>> including a python3 binary in Sage by default with "python3" right
>> there in the "sage -sh" path...
>
On Thursday, August 24, 2017 at 1:30:25 PM UTC-7, William wrote:
>
> I'm not sure what the status is these days, but we may want to stop
> including a python3 binary in Sage by default with "python3" right
> there in the "sage -sh" path...
As far as I understand, having python3 included in sag
Hi,
I'm not sure what the status is these days, but we may want to stop
including a python3 binary in Sage by default with "python3" right
there in the "sage -sh" path... It randomly and confusingly breaks a
lot of stuff related to Jupyter kernels getting installed into Sage.
You can observe som
Do you volunteer to weed out spam? :)
--
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
Has the time come for sage-support to allow posts by non-members? Some
questions are not ideal for the Q&A format of ask.sagemath but we don't
necessarily want to ask people to have to wait for signing up on
sage-support ... or waiting for approval as members to ask a simple
question.
See
h
On Thu, Aug 24, 2017 at 4:45 PM, Jeroen Demeyer wrote:
> On 2017-08-23 23:44, Marc Masdeu wrote:
>>
>> This is essentially what they are supposed to be.
>
>
> But it's not what your package does! You are using "sage" all over the
> place.
I'm probably missing something, but I don't see where it's
On Thu, Aug 24, 2017 at 3:43 PM, mforets wrote:
>
> Hi Erik,
> OK thanks for the link, I will go ahead with PyJulia.
>
> I think the problem is the returned times symbol, which is a fancy "x", and
> that one requires Python 3 to be properly parsed.
To be clear, that doesn't *require* Python 3; it
On 2017-08-23 23:44, Marc Masdeu wrote:
This is essentially what they are supposed to be.
But it's not what your package does! You are using "sage" all over the
place.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this g
sagenb is installed by pip, which pulls packages from the net; whatever
comes up as the "stable" version,
gets installed. We used to pin down versions, but don't do this any more.
You can look at the output of
./sage --pip list
to see what versions you have.
Sagenb explicitly needs the followin
Hi Erik,
OK thanks for the link, I will go ahead with PyJulia.
I think the problem is the returned times symbol, which is a fancy "x", and
that one requires Python 3 to be properly parsed.
El jueves, 24 de agosto de 2017, 11:59:00 (UTC+2), Erik Bray escribió:
>
> On Wed, Aug 23, 2017 at 6:33 P
On Thursday, August 24, 2017 at 4:54:48 AM UTC-4, Jori Mäntysalo wrote:
>
> On Thu, 24 Aug 2017, Dima Pasechnik wrote:
>
> > although it very well might be due to its dependencies, like flask,
> > etc., updated to newer versions, e.g. for the purpose of python3
> > compatibility.
>
> OK. What
On Wed, Aug 23, 2017 at 6:33 PM, mforets wrote:
> Hello,
> I'm writing an "expect" interface to use Julia from Sage, copy pasted from
> the Matlab `interfaces/matlab.py`.
>
> For the moment, the code is here:
> https://gist.github.com/mforets/26d42220946fba8f8e1feb8208783231
> Of course i'll add a
On Wed, Aug 23, 2017 at 5:56 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> One thing (IMHO much more important than the "cookie cutter" buisness) is to
> actually have a community supported language for SageMath in travis [1]. My
> aim is to allow the following in the travis script
Oh
On Thu, 24 Aug 2017, Dima Pasechnik wrote:
although it very well might be due to its dependencies, like flask,
etc., updated to newer versions, e.g. for the purpose of python3
compatibility.
OK. What packages or parts have been updated lately?
--
Jori Mäntysalo
although it very well might be due to its dependencies, like flask, etc.,
updated to newer versions, e.g. for the purpose of python3 compatibility.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
check out the upstream sagenb repo and do git blame, indeed.
--
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 th
20 matches
Mail list logo
