Re: [sage-devel] First Joint GAP-​Sage Days (St Andrews, January 2016)

[Samuel Lelievre]

2015-10-12 22:45:08 UTC+2, Snark:
>
> Le lundi 12 oct. 2015 à 13:02:38 (-0700), Volker Braun a écrit : 
> > On Monday, October 12, 2015 at 3:46:29 PM UTC+2, Snark wrote: 
> > > 
> > > Does that mean that the libgap in sagemath will get part of upstream 
> GAP? 
> > > 
> > 
> > A better interop between Sage and GAP is definitely desirable. I don't 
> > think anybody has a clear plan at this point but I'll be at the meeting 
> ;-) 
> > 
>
> We are uncomfortable with packaging sage-the-distribution's libgap in 
> Debian, 
> because as the name doesn't say it's sage-specific, we might be in some 
> trouble 
> if GAP were to release a real-GAP libgap (even in some years... Debian is 
> about 
> long-term). 
>
> So if that lib could get upstream's blessing (or just get renamed 
> libsagegap), 
> that would make things easier.
>

See a discussion of that point on the gap development list at

https://mail.gap-system.org/pipermail/gap/2015-October/000176.html 

-- 
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.

Re: [sage-devel] Graph() construction with edge function

[Nathann Cohen]

Helloo,

> Yes, I think if the documentation screams "implements a symmetric relation"
> that would be a big improvement.  And maybe a doctest illustrating how it
> can go bad?

I added a mention that the function should be symmetric, and just
pushed a new doctest for that:


http://git.sagemath.org/sage.git/commit/?id=3b724240f9aba068d4495b4600c3f4a9190d5043

(still on #19390)

Have fuun,

Nathann

-- 
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.

[sage-devel] Re: [sage-trac] #10295: Upgrading pexpect

[William Stein]

On Thursday, October 15, 2015, Bill Page  wrote:

> The version of pexpect with the new option is still a branch called
>
> https://github.com/pexpect/pexpect/tree/superfluous-sleep
>
> I think they are waiting for us to say that it works with Sage.
>

Make sure to test the latency/speed/overhead using timeout.  1000x speed
slowdowns were why we stopped using official pexpect after a rewrite they
did.



> Sorry, I really dont understand what is required in order to update a
> branch on git.sagemath.org
> 
>
>
>
> On 15 October 2015 at 21:32, François Bissey <
> francois.bis...@canterbury.ac.nz
> > wrote:
>
>> On 10/16/15 14:29, kcrisman wrote:
>>
>>> Though I guess one would have to upgrade sagenb and pexpect
>>> simultaneously?
>>>
>>  You got that part right, it will have to be simultaneous.
>> Bill can you update the branch for a version with the commit in
>> question included? Is it even released yet?
>>
>> Francois
>>
>>
>> --
>> 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.
>>
>
> --
> 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.
>


-- 
Sent from my massive iPhone 6 plus.

-- 
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.

Re: [sage-devel] First Joint GAP-​Sage Days (St Andrews, January 2016)

['Julien Puydt' via sage-devel]

Le 16/10/2015 11:20, Samuel Lelievre a écrit :


2015-10-12 22:45:08 UTC+2, Snark:

Le lundi 12 oct. 2015 à 13:02:38 (-0700), Volker Braun a écrit :
 > On Monday, October 12, 2015 at 3:46:29 PM UTC+2, Snark wrote:
 > >
 > > Does that mean that the libgap in sagemath will get part of
upstream GAP?
 > >
 >
 > A better interop between Sage and GAP is definitely desirable. I
don't
 > think anybody has a clear plan at this point but I'll be at the
meeting ;-)
 >

We are uncomfortable with packaging sage-the-distribution's libgap
in Debian,
because as the name doesn't say it's sage-specific, we might be in
some trouble
if GAP were to release a real-GAP libgap (even in some years...
Debian is about
long-term).

So if that lib could get upstream's blessing (or just get renamed
libsagegap),
that would make things easier.


See a discussion of that point on the gap development list at

https://mail.gap-system.org/pipermail/gap/2015-October/000176.html


Thanks!

Snark on #sagemath

--
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.

[sage-devel] I > 0 is true

[Daniel Krenn]

sage: bool(I>0)
True

Is there a ticket for this on trac?

Daniel

--
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.

[sage-devel] Two remarks (bugs?) about the patchbot

[Nathann Cohen]

Hello everybody,

I have two remarks to make about the patchbot, and I have no idea if I am just
misinterpreting/misreading or if there is something wrong:

1) The ticket at #19353 fails to build the doc. I built it manually and noticed
   a missing reference ([Kohnert07]), though this missed reference *does not
   appear* in the log. So the reason why the doc fails is not reported
   (anymore?) which complicates debugging.

2) This ticket has a dependency #19335 which *defines* the reference, but the
   patchbot did not load it first (thus the message).

   Probably a consequence of the fact that this ticket (#19335) is *closed* but
   not merged in the latest beta (except in Volker's computer).

Good evenings,

Nathann

-- 
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.

Re: [sage-devel] Graph() construction with edge function

[Rob Beezer]

Nathann - Looks great - thanks!  -Rob

On Friday, October 16, 2015 at 3:38:41 AM UTC-7, Nathann Cohen wrote:
>
> Helloo, 
>
> > Yes, I think if the documentation screams "implements a symmetric 
> relation" 
> > that would be a big improvement.  And maybe a doctest illustrating how 
> it 
> > can go bad? 
>
> I added a mention that the function should be symmetric, and just 
> pushed a new doctest for that: 
>
> 
> http://git.sagemath.org/sage.git/commit/?id=3b724240f9aba068d4495b4600c3f4a9190d5043
>  
>
> (still on #19390) 
>
> Have fuun, 
>
> Nathann 
>

-- 
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.

[sage-devel] Re: Two remarks (bugs?) about the patchbot

[Frédéric Chapoton]

Hello,
I know that the patchbot seems to have spurious problems with the doc 
precisely with the official releases. But this is not the case here.

you can find the doc failure in the doc plugin result by searching for 
WARNING:

http://patchbot.sagemath.org/log/19353/Ubuntu/15.04/x86_64/3.19.0-30-generic/kevin-VirtualBox/2015-10-16%2015:19:49?plugin=plugins.docbuild&diff=/log/0/Ubuntu/15.04/x86_64/3.19.0-30-generic/kevin-VirtualBox/2015-10-16%2000%3A40%3A29&ticket=19353&base=6.10.beta0

Frederic

Le vendredi 16 octobre 2015 17:37:42 UTC+2, Nathann Cohen a écrit :
>
> Hello everybody, 
>
> I have two remarks to make about the patchbot, and I have no idea if I am 
> just 
> misinterpreting/misreading or if there is something wrong: 
>
> 1) The ticket at #19353 fails to build the doc. I built it manually and 
> noticed 
>a missing reference ([Kohnert07]), though this missed reference *does 
> not 
>appear* in the log. So the reason why the doc fails is not reported 
>(anymore?) which complicates debugging. 
>
> 2) This ticket has a dependency #19335 which *defines* the reference, but 
> the 
>patchbot did not load it first (thus the message). 
>
>Probably a consequence of the fact that this ticket (#19335) is 
> *closed* but 
>not merged in the latest beta (except in Volker's computer). 
>
> Good evenings, 
>
> Nathann 
>

-- 
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.

Re: [sage-devel] Re: Two remarks (bugs?) about the patchbot

[Nathann Cohen]

> I know that the patchbot seems to have spurious problems with the doc
> precisely with the official releases. But this is not the case here.

I see. I first wrote this bug report about #19344 then changed the
ticket number to simplify the bug report (which thus becomes wrong, as
you noticed :-/). #19344 is what I described and I do not see the
warning that you reported in the corresponding log.

#19344 depends on the ticket that I reported, which in turns depends
on the ticket that is "closed but not merged".

Sorry for the erroneous report.

Nathann

-- 
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.

[sage-devel] Ping for review: Element.__hash__ rework

[Nils Bruin]

As far as doctests go, we have now figured out how to successfully remove 
the problematic "hash(str(a))" implementation on sage Element. The ticket 
just needs some trivial doctest additions to make a beancounting patchbot 
plugin happy. The changes on the ticket are pretty straightforward, but the 
effects can be relatively far-reaching. So, positive review & merge early 
in the 6.10 cycle might be a good idea to shake out unforeseen sideeffects. 
Reviews welcome:

http://trac.sagemath.org/ticket/19016

-- 
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.

Re: [sage-devel] Re: Two remarks (bugs?) about the patchbot

[Frédéric Chapoton]

in the logs for 19344:

+[graphs   ] None:3: WARNING: citation not found: Kohnert07

Le vendredi 16 octobre 2015 19:29:14 UTC+2, Nathann Cohen a écrit :
>
> > I know that the patchbot seems to have spurious problems with the doc 
> > precisely with the official releases. But this is not the case here. 
>
> I see. I first wrote this bug report about #19344 then changed the 
> ticket number to simplify the bug report (which thus becomes wrong, as 
> you noticed :-/). #19344 is what I described and I do not see the 
> warning that you reported in the corresponding log. 
>
> #19344 depends on the ticket that I reported, which in turns depends 
> on the ticket that is "closed but not merged". 
>
> Sorry for the erroneous report. 
>
> Nathann 
>

-- 
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.

Re: [sage-devel] Re: Two remarks (bugs?) about the patchbot

[Nathann Cohen]

> in the logs for 19344:
>
> +[graphs   ] None:3: WARNING: citation not found: Kohnert07

I see. So this information will not be found in the shortlog, and only
in the log.

Nathann

-- 
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.

Re: [sage-devel] I > 0 is true

[Vincent Delecroix]

On 16/10/15 11:52, Daniel Krenn wrote:
> sage: bool(I>0)
> True
>
> Is there a ticket for this on trac?

What answer would you expect?

sage: CC(0,1) > CC(0,0)
True

Sage uses lexicographic ordering for CC.

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.

Re: [sage-devel] I > 0 is true

[John Cremona]

On 16 October 2015 at 17:16, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> On 16/10/15 11:52, Daniel Krenn wrote:
>> sage: bool(I>0)
>> True
>>
>> Is there a ticket for this on trac?
>
> What answer would you expect?

Obviously, any mathematician would expect the mathematically sensible
answer of "undefined".  And yes, I do know why that is not what
happens in python.

John

>
> sage: CC(0,1) > CC(0,0)
> True
>
> Sage uses lexicographic ordering for CC.
>
> 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.

-- 
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.

Re: [sage-devel] I > 0 is true

[Nils Bruin]

On Friday, October 16, 2015 at 2:22:41 PM UTC-7, John Cremona wrote:
>
> Obviously, any mathematician would expect the mathematically sensible 
> answer of "undefined".  And yes, I do know why that is not what 
> happens in python. 
>

Wrong, that IS what happens in python

Python 2.7.10 (default, Sep 24 2015, 17:50:09) 
[GCC 5.1.1 20150618 (Red Hat 5.1.1-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> complex(1,0)> complex(0,1)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: no ordering relation is defined for complex numbers

It's just the mathematical software sage that goes for the mathematically 
dubious answer.

-- 
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.

[sage-devel] Re: I > 0 is true

[Ralf Stephan]

On Friday, October 16, 2015 at 4:52:20 PM UTC+2, Daniel Krenn wrote:
>
> sage: bool(I>0) 
> True 
>
> Is there a ticket for this on trac? 
>

http://trac.sagemath.org/ticket/17700
which practically depends on 
http://trac.sagemath.org/ticket/19312

Note that with the latter comes ex.holds() so you could in the future
get an exception from bool(I>0) but the result Undefined/Undecidable
from (I>0).holds()

Also, this has nothing to do with CC because

sage: type(I)




Best,

-- 
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.