On Wednesday, March 28, 2018 at 1:52:17 AM UTC-5, Simon King wrote:
>
> Hi Andrey and Saad,
>
> On 2018-03-28, Andrey Novoseltsev
> wrote:
> > On Tuesday, 27 March 2018 18:03:48 UTC-6, saad khalid wrote:
> >>
> >> Why not assume by default that when someone enters a
On Wed, Mar 28, 2018 at 11:01 PM, saad khalid wrote:
> On Wednesday, March 28, 2018 at 1:52:17 AM UTC-5, Simon King wrote:
>>
>> Hi Andrey and Saad,
>>
>> On 2018-03-28, Andrey Novoseltsev wrote:
>> > On Tuesday, 27 March 2018 18:03:48 UTC-6, saad khalid
On Tuesday, March 27, 2018 at 8:39:50 AM UTC-4, Erik Bray wrote:
>
> On Sun, Mar 25, 2018 at 4:49 PM, Simon King > wrote:
> > Hi!
> >
> > On 2018-03-25, Volker Braun wrote:
> >> On Sunday, March 25, 2018 at 2:51:46 PM UTC+2, Dima Pasechnik
I'm wondering if this is a known bug. I'm using Sagemath8.1 in Jupyter
Notebook
Consider the sequence:
var("x,y,z,t")
f(x,y)=sin(x*y)
Df=f.gradient()
The command
plot_vector_field(Df,(x,0,1),(y,0,1))
produces a nice vector field, but the command
streamline_plot(Df,(x,0,1),(y,0,1))
raises an
Hello,
I've tried to compile sage-8.1 on a linux server, and I get the following
error:
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
* package: numpy-1.13.3.p0
log file:
This looks like a gcc/gfortran problem.
Could you post also
logs/pkgs/config.log ?
You might consider forcing building gcc, see SAGE_INSTALL_GCC in
http://doc.sagemath.org/html/en/installation/source.html#environment-variables
On Thursday, March 29, 2018 at 5:18:09 PM UTC+1, Paul Mercat
On Thu, Mar 29, 2018 at 11:56 AM, Nils Bruin wrote:
> On Thursday, March 29, 2018 at 10:37:03 AM UTC-7, William wrote:
>>
>>
>> It's surprisingly easy to implement this, due to how Robert Bradshaw
>> rewrote this part of the Sage preparser.If you define this
>> function in a
On Thursday, March 29, 2018 at 10:37:03 AM UTC-7, William wrote:
>
>
> It's surprisingly easy to implement this, due to how Robert Bradshaw
> rewrote this part of the Sage preparser.If you define this
> function in a notebook or command line sage session:
>
> def RealNumber(s):
> if
On Thursday, March 29, 2018 at 11:57:32 AM UTC-7, William wrote:
>
>
> Thanks -- I should have added that the above was a quick "proof of
> concept".
>
> In fact, letting 1.3e5 still be parsed as a float literal would make this
modified behaviour just extremely annoying rather than completely
I just started 8.2.rc0 in a terminal and observed a change in the banner.
Is this an expected behavior or something goes wrong ?
confetti:sage dcoudert$ ./sage
┌┐
│ SageMath version 8.2.beta8, Release Date: 2018-03-10
Thanks for reporting.
This is handled by
https://trac.sagemath.org/ticket/25056
Best wishes,
Eric.
--
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
I'm not entirely sure how to implement this though, if we don't want it to
be the global behavior. I was considering just implementing it for the
rank() function, but I'm assuming it processes the input into the function
before it starts running the actual function, right? So it isn't just
The obvious answer: Show a warning if you test field elements for primality
* easy to implement using standard Python machinery
* does not introduce backward-incompatibile changes
* is mathematically correct
* informative to casual users
* unlikely to give spurious warnings in existing code
--
On Wednesday, March 28, 2018 at 9:20:17 AM UTC-4, Jeroen Demeyer wrote:
>
> On 2018-03-28 15:05, Simon King wrote:
> > By "graphical", I really mean "interactively".
>
> It seems to me that those would be two different things:
>
> (1) A notebook widget for inputting matrices
>
>
This already
14 matches
Mail list logo