Re: [sage-devel] Jupyterhub kernel and SAGE_ROOT

[François Bissey]

> On 21/11/2018, at 03:52, Jeroen Demeyer  wrote:
> 
> On 2018-11-06 19:07, François Bissey wrote:
>> SAGE_LOCAL is another story,
>> however we probably could figure it out from the python configuration rather
>> than a seed.
> 
> Isn't SAGE_LOCAL == sys.prefix

Should be. But following this thread I changed the way I patch
env.py and now I have
_add_variable_or_fallback('SAGE_LOCAL',  sysconfig.get_config_var("prefix”))

François

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Jupyterhub kernel and SAGE_ROOT

[Erik Bray]

On Fri, Nov 16, 2018 at 2:38 PM Luca De Feo  wrote:
>
> > How fast will new SageMath versions be packaged? I suppose that fast
> > enought, and those needing the bleeding edge version can compile it
> > themself.
>
> I agree. Ubuntu bionic has 8.1, cosmic has 8.3.
>
> Unless we screw up and make Sage impossible to package (see mail by
> Samuel on Debian freeze), these will follow closely enough for the
> average user.

That's funny wording.  I would consider Sage effectively impossible to
package.  Sure, it's been *done*.  We've been doing it.  But it
requires an almost absurd amount of overhead to get right :)

> > I have no previous experience on containers, but I guess they are here to
> > stay and I should learn them.
>
> I got to the point where I consider Docker as fundamental a tool  as Git.

I wouldn't go quite that far, but there's still hardly a day goes by I
don't use one :)

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: doctest result depending on --long

[Frédéric Chapoton]

known issue, see https://trac.sagemath.org/ticket/26586

F

Le mardi 20 novembre 2018 17:26:17 UTC+1, Martin R a écrit :
>
> Dear all!
>
> I am in need of help again.  At https://trac.sagemath.org/ticket/25864 I 
> have a doctest whose output seems to depend on whether the option --long is 
> passed or not.
>
> The doctest is in src/sage/combinat/posets/poset_examples.py:
>
>
> -
> EXAMPLES::
>
> sage: P = posets.YoungDiagramPoset(Partition([2,2])); P
> Finite meet-semilattice containing 4 elements
> sage: P.cover_relations()
>
> -
>
> I now get (with the branch on the ticket applied)
>
> sage -t --long src/sage/combinat/posets/poset_examples.py
> **
> File "src/sage/combinat/posets/poset_examples.py", line 1400, in 
> sage.combinat.posets.poset_examples.Posets.YoungDiagramPoset
> Failed example:
> P.cover_relations()
> Expected nothing
> Got:
> [[(0, 0), (0, 1)], [(0, 0), (1, 0)], [(0, 1), (1, 1)], [(1, 0), (1, 
> 1)]]
>
> versus
>
> sage -t  src/sage/combinat/posets/poset_examples.py 
> **
> File "src/sage/combinat/posets/poset_examples.py", line 1400, in 
> sage.combinat.posets.poset_examples.Posets.YoungDiagramPoset
> Failed example:
> P.cover_relations()
> Expected nothing
> Got:
> [[(0, 0), (1, 0)], [(0, 0), (0, 1)], [(1, 0), (1, 1)], [(0, 1), (1, 
> 1)]]
> **
> (note that the order of the output changed)
>
> There is one "long" doctest in the same file:
>
> -
> sage: posets.SSTPoset([3,2]).bottom()  # long time (6s on 
> sage.math, 2012)
> [[1, 1, 1], [2, 2]]
>
> -
>
> If I remove the long from there, the difference goes away, and I get the 
> "long" version.
>
> If I run the doctest in the console, I get the "long" version.
>
> How can I debug this?
>
> Help is much appreciated!
>
> Martin
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] doctest result depending on --long

[Dima Pasechnik]

Just sort the output in the doctest...

On Tue, 20 Nov 2018 at 16:26, 'Martin R' via sage-devel <
sage-devel@googlegroups.com> wrote:

> Dear all!
>
> I am in need of help again.  At https://trac.sagemath.org/ticket/25864 I
> have a doctest whose output seems to depend on whether the option --long is
> passed or not.
>
> The doctest is in src/sage/combinat/posets/poset_examples.py:
>
>
> -
> EXAMPLES::
>
> sage: P = posets.YoungDiagramPoset(Partition([2,2])); P
> Finite meet-semilattice containing 4 elements
> sage: P.cover_relations()
>
> -
>
> I now get (with the branch on the ticket applied)
>
> sage -t --long src/sage/combinat/posets/poset_examples.py
> **
> File "src/sage/combinat/posets/poset_examples.py", line 1400, in
> sage.combinat.posets.poset_examples.Posets.YoungDiagramPoset
> Failed example:
> P.cover_relations()
> Expected nothing
> Got:
> [[(0, 0), (0, 1)], [(0, 0), (1, 0)], [(0, 1), (1, 1)], [(1, 0), (1,
> 1)]]
>
> versus
>
> sage -t  src/sage/combinat/posets/poset_examples.py
> **
> File "src/sage/combinat/posets/poset_examples.py", line 1400, in
> sage.combinat.posets.poset_examples.Posets.YoungDiagramPoset
> Failed example:
> P.cover_relations()
> Expected nothing
> Got:
> [[(0, 0), (1, 0)], [(0, 0), (0, 1)], [(1, 0), (1, 1)], [(0, 1), (1,
> 1)]]
> **
> (note that the order of the output changed)
>
> There is one "long" doctest in the same file:
>
> -
> sage: posets.SSTPoset([3,2]).bottom()  # long time (6s on
> sage.math, 2012)
> [[1, 1, 1], [2, 2]]
>
> -
>
> If I remove the long from there, the difference goes away, and I get the
> "long" version.
>
> If I run the doctest in the console, I get the "long" version.
>
> How can I debug this?
>
> Help is much appreciated!
>
>
> Martin
>
> --
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] doctest result depending on --long

['Martin R' via sage-devel]

Dear all!

I am in need of help again.  At https://trac.sagemath.org/ticket/25864 I 
have a doctest whose output seems to depend on whether the option --long is 
passed or not.

The doctest is in src/sage/combinat/posets/poset_examples.py:

-
EXAMPLES::

sage: P = posets.YoungDiagramPoset(Partition([2,2])); P
Finite meet-semilattice containing 4 elements
sage: P.cover_relations()
-

I now get (with the branch on the ticket applied)

sage -t --long src/sage/combinat/posets/poset_examples.py
**
File "src/sage/combinat/posets/poset_examples.py", line 1400, in 
sage.combinat.posets.poset_examples.Posets.YoungDiagramPoset
Failed example:
P.cover_relations()
Expected nothing
Got:
[[(0, 0), (0, 1)], [(0, 0), (1, 0)], [(0, 1), (1, 1)], [(1, 0), (1, 1)]]

versus

sage -t  src/sage/combinat/posets/poset_examples.py 
**
File "src/sage/combinat/posets/poset_examples.py", line 1400, in 
sage.combinat.posets.poset_examples.Posets.YoungDiagramPoset
Failed example:
P.cover_relations()
Expected nothing
Got:
[[(0, 0), (1, 0)], [(0, 0), (0, 1)], [(1, 0), (1, 1)], [(0, 1), (1, 1)]]
**
(note that the order of the output changed)

There is one "long" doctest in the same file:
-
sage: posets.SSTPoset([3,2]).bottom()  # long time (6s on 
sage.math, 2012)
[[1, 1, 1], [2, 2]]
-

If I remove the long from there, the difference goes away, and I get the 
"long" version.

If I run the doctest in the console, I get the "long" version.

How can I debug this?

Help is much appreciated!

Martin

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Implementing rings of coordinates

[VulK]

Dear all,
I am trying to implement the ring of coordinates of a Lie group in the 
perspective of Peter-Weyl theorem.


Concretely I would like to define a polynomial ring with infinitely many 
generators each depending on two points on a lattice. These generators 
satisfy many relations but, for the moment, I am happy to forget this fact.  
Is this possible in the current sage framework? Which are the classes I 
should inherit from?


From a quick look at available classes it looks like InfinitePolynomialRing 
and InfinitePolynomial might be the one I am after but I do not see how to 
change the indexing sets as I need apart from brute force: I could keep a 
dictionary and hack _repr_ accordingly. Any better idea?


In a second moment I would like to be able to evaluate the element of this 
ring at point on the group; is there a way to make them callable?

Thanks
S.


--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Jupyterhub kernel and SAGE_ROOT

[Jeroen Demeyer]

On 2018-11-06 19:07, François Bissey wrote:

SAGE_LOCAL is another story,
however we probably could figure it out from the python configuration rather
than a seed.


Isn't SAGE_LOCAL == sys.prefix

--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] review request

['Martin R' via sage-devel]

Dear all,

the ticket #25662  (wrong contains 
in PartitionDiagrams) fixes a small bug that may hurt when computing in the 
diagram algebra.

Since it's finished for three months now, it would be great if someone 
could have a look at it!

Many thanks,

Martin

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.