>Suppose you have function A that calls function B a lot over a loop, and
> both of them can take advantage of the canonical labeling of the DiGraph. If
> you do not have a HasseDiagram class, then A would have to convert the
> canonical labeling, then convert back every time it called B, which
I raised some objections on the ticket.
David
On Fri, Jan 22, 2016 at 7:38 AM, Nathann Cohen
wrote:
> The 'constructor' file is being renamed to 'finite_field_constructor'
> in the following ticket:
>
> http://trac.sagemath.org/ticket/19941
>
> Nathann
>
> On 22 January 2016 at 12:13, Nathan
Fredrik Johansson wrote:
> Arb (which is now in Sage) permits computing incomplete gamma
> functions with rigorous error bounds over arbitrary-precision
> real/complex (interval) fields.
Incidentally, the sage bindings (over complex balls) need review:
http://trac.sagemath.org/ticket/19082
--
M
On Friday, 22 January 2016 10:23:18 UTC, Jeroen Demeyer wrote:
>
> On 2016-01-22 11:13, Nathann Cohen wrote:
> > Hello everybody,
> >
> > The title of the following module is 'Finite Fields'. Its contains
> > code related to finite fields.
> >
> > sage/rings/finite_rings/constructor.py
On Friday, 22 January 2016 17:23:06 UTC, David Joyner wrote:
>
> On Fri, Jan 22, 2016 at 2:29 AM, Dima Pasechnik > wrote:
> >
> >
> > On Thursday, 21 January 2016 07:16:45 UTC, Jeroen Demeyer wrote:
> >>
> >> On 2016-01-21 00:29, Dima Pasechnik wrote:
> >> > Surely, if the official nauty g
On Friday, January 22, 2016 at 1:03:59 AM UTC-6, Nathann Cohen wrote:
>
> >Do you want DiGraph to have methods like rank or is_chain?
>
> Of course not. The idea was to have Poset carry a DiGraph
> _hasse_diagram instead of a HasseDiagram object, and to [move/merge]
> the methods from Hass
I would vote yes if the concerns presented by François are addresed.
--
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 po
On Fri, Jan 22, 2016 at 10:15 AM, srozensz
wrote:
> sage: A. = Zq(4)
> sage: A(0)^0
> O(2^0)
Thanks. This is now http://trac.sagemath.org/ticket/19943
David
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and s
On Fri, Jan 22, 2016 at 2:29 AM, Dima Pasechnik wrote:
>
>
> On Thursday, 21 January 2016 07:16:45 UTC, Jeroen Demeyer wrote:
>>
>> On 2016-01-21 00:29, Dima Pasechnik wrote:
>> > Surely, if the official nauty got another licence it would have solved
>> > the problem easier.
>>
>> Maybe you could
On Friday, January 22, 2016 at 4:49:23 AM UTC-5, Andres Erbsen wrote:
>
> Hello,
>
> I encountered some unexpected behavior when using solve() with anonymous
> symbols generated using SR.symbol(). The returned by solve are not the same
> as the ones passed in (even though they look the same). H
Hello,
I have noticed an unexpected behavior when trying to evaluate 0^0 in
unramified extensions of Zp. Here is an example:
sage: A. = Zq(4)
sage: A(0)^0
O(2^0)
Compare with:
sage: B = Zp(2)
sage: B(0)^0
1 + O(2^20)
I am using Sage 6.10 on MacOS X version 10.11.
--
You received this me
Hi
Yes, I am getting some queries directly to me as well (as PPA maintainer).
The SAGE_ROOT/relocate-once.py is becoming less compatible with
dpkg-buildpackage, which wants to manage the files, and not have them
changed after installation.
We're thinking of a new simpler package, which contains t
On Tuesday, January 12, 2016 at 10:15:00 AM UTC-7, Volker Braun wrote:
>
> On Tuesday, January 12, 2016 at 3:30:22 PM UTC+1, Jan Groenewald wrote:
>>
>> Funny thing is, basic operations ad plotting work fine, whereas I thought
>> if relocate-once.py failed sage would not be able to find any of i
Thanks Karl-Philip Richter for reporting these broken links.
Harald, could we set up a redirection from
http://www.sagemath.org/mirror/*
to
http://files.sagemath.org/*
Note that we already have a redirection from
http://www.sagemath.org/src-old/
to
http://old.files.sagemath.org/sr
The 'constructor' file is being renamed to 'finite_field_constructor'
in the following ticket:
http://trac.sagemath.org/ticket/19941
Nathann
On 22 January 2016 at 12:13, Nathann Cohen wrote:
> Hello everybody,
>
> The title of the following module is 'Finite Fields'. Its contains
> code rel
> Of course not, but we need to deprecate the old modules.
Yes yes of course.
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...@goog
On 2016-01-22 11:41, Nathann Cohen wrote:
Do you see have any objection to setting things right?
Of course not, but we need to deprecate the old modules.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop re
> I can do better:
>
> src/sage/rings/real_lazy.pyx
>
> contains code for real and *complex* lazy numbers.
Nice. I hope nobody will beat that.
Do you see have any objection to setting things right?
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-deve
On 2016-01-22 11:13, Nathann Cohen wrote:
Hello everybody,
The title of the following module is 'Finite Fields'. Its contains
code related to finite fields.
sage/rings/finite_rings/constructor.py
Is it just me, or is there a noticeable discrepancy between the
filename and the content/titl
Thank you, Dima,
> On 22 Jan 2016, at 09:49, Dima Pasechnik wrote:
>
> Software Carpentry, see http://software-carpentry.org, is a charity that does
> "Teaching basic lab skills for research computing". But goes beyond that;
> their workshops can include more nontrivial components, e.g. recent
Hi Dima,
I’m not sure how much time I can contribute, but I’m in principle
interested and would appreciate being kept in the loop.
Cheers,
Martin
Dima Pasechnik writes:
> Software Carpentry, see http://software-carpentry.org, is a charity that
> does "Teaching basic lab skills for research comp
Hello everybody,
The title of the following module is 'Finite Fields'. Its contains
code related to finite fields.
sage/rings/finite_rings/constructor.py
Is it just me, or is there a noticeable discrepancy between the
filename and the content/title?
Thanks,
Nathann
--
You received this m
Hello,
I encountered some unexpected behavior when using solve() with anonymous
symbols generated using SR.symbol(). The returned by solve are not the same
as the ones passed in (even though they look the same). Here is a minimal
example:
x sage: x = SR.symbol(); x
symbol151
sage: sol = solve(
Software Carpentry, see http://software-carpentry.org, is a charity that
does "Teaching basic lab skills for research computing". But goes beyond
that; their workshops can include more nontrivial components, e.g. recently
GAP people conducted such an introductory GAP workshop:
https://kkwakwa.gi
A related question now that I'm thinking about refactoring:
can we drop the in-place methods like __iadd__? May we assume that no
Element will need in-place methods with coercion?
The problem is when classes want to implement a special __add__ without
coercion (that is legitimate). If those c
On Fri, Jan 22, 2016 at 12:58 AM, Buck Evan wrote:
> Fredrik:
> Thank you for your thoughtful reply!
>
> On Thu, Jan 21, 2016 at 2:48 PM Fredrik Johansson
> wrote:
>>
>> Arb (which is now in Sage) permits computing incomplete gamma
>> functions with rigorous error bounds over arbitrary-precision
26 matches
Mail list logo
