Re: [sage-devel] Re: making database_gap (starting from GAP 4.9) standard - please vote

[David Roe]

On Sun, Feb 18, 2018 at 8:15 AM, Simon King  wrote:

> Hi Dima,
>
> in fact I am very happy that the authors of the SmallGroups library has
> finally agreed to make it GPL compatible.
>
> So, +1 to making database_gap standard.
>

+1 from me as well.
David


>
> Best regards,
> Simon
>
>
> Am Sonntag, 18. Februar 2018 00:01:50 UTC+1 schrieb Dima Pasechnik:
>>
>> GAP 4.9 (a release candidate, released 1st Feb) has  smallgrps and
>> transgrps, two GAP packages/libraries which are extremely useful, with
>> GPL-compatible licenses. In the past (and up to current GAP 4.8)
>> they had licenses non-GPL compatible licenses, preventing them from being
>> made standard.
>>
>> It's about 60MB extra, but it would really make it possible to distribute
>> an essentially standard configuration of GAP, reducing the chances of
>> various mishaps, and easing the support a lot.
>>
>> Thus I'm calling for a vote on this: to make database_gap standard as
>> soon as license permits (i.e. as soon as we update to GAP 4.9).
>>
>> Dima
>>
>>
>>
> --
> 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] sage-* lists on news.gmane.org?

[Simon King]

Hi!

Since quite some time I prefer to read the sage mailing lists (-devel, 
-support, -release etc) using slrn, but since a couple of days I get a 
Run-Time Error stating that the server news.gmane.org couldn't be resolved.

Is that a permanent problem?

Best regards,
Simon

-- 
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: making database_gap (starting from GAP 4.9) standard - please vote

[Simon King]

Hi Dima,

in fact I am very happy that the authors of the SmallGroups library has 
finally agreed to make it GPL compatible.

So, +1 to making database_gap standard.

Best regards,
Simon

Am Sonntag, 18. Februar 2018 00:01:50 UTC+1 schrieb Dima Pasechnik:
>
> GAP 4.9 (a release candidate, released 1st Feb) has  smallgrps and 
> transgrps, two GAP packages/libraries which are extremely useful, with 
> GPL-compatible licenses. In the past (and up to current GAP 4.8)
> they had licenses non-GPL compatible licenses, preventing them from being 
> made standard.
>
> It's about 60MB extra, but it would really make it possible to distribute 
> an essentially standard configuration of GAP, reducing the chances of 
> various mishaps, and easing the support a lot.
>
> Thus I'm calling for a vote on this: to make database_gap standard as soon 
> as license permits (i.e. as soon as we update to GAP 4.9).
>
> Dima
>
>  
>

-- 
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: Sage 8.1 eats memory while 7.5.1 did not

[Travis Scrimshaw]

As a variant of option 3: install a system-wide ssl after building Sage: I 
believe this just requires rebuild python:

 sage -f python2

At least, this was all I had to do on some older version of Sage (I forget 
which since it has been over a year, maybe even 2, since I did this).

Best,
Travis


On Saturday, February 17, 2018 at 1:05:21 PM UTC-6, Samuel Lelievre wrote:
>
> Sat 2018-02-17 07:38:20 UTC, Ralf Stephan:
> >
> > On Friday, February 16, 2018 at 10:05:02 AM UTC+1, Dima Pasechnik wrote:
> >>
> >> guppy.hpy() finds 149 objects 
> >> dict of sympy.core.assumptions.ManagedProperties
> >> on the heap
> >
> > The solution of the original issue did not involve sympy so I was trying 
> to reproduce this, but when trying to SAGE_ROOT/local/bin/pip install guppy 
> I got
> >
> > pip is configured with locations that require TLS/SSL, however the ssl 
> module in Python is not available.
> > Collecting guppy
> >   Could not fetch URL https://pypi.python.org/simple/guppy/: There was 
> a problem confirming the ssl certificate: Can't connect to HTTPS URL 
> because the SSL module is not available. - skipping
> >   Could not find a version that satisfies the requirement guppy (from 
> versions: )
> > No matching distribution found for guppy
> >
> > How did you install guppy?
>
> Installing extra packages with Sage's pip as in
>
> sage --pip install guppy
>
> will only succeed if Sage's Python has ssl support.
>
> For this to be the case, you need one of the following:
>
> - have system-wide ssl support before building Sage.
>   In Ubuntu, this would be achieved by running
>
>   sudo apt full-upgrade
>   sudo apt install openssl libssl-dev
>
> - install ssl support before building Sage:
>
>   ./sage -i openssl
>   make
>
> - install ssl support once Sage is already built:
>
>   sage -i openssl
>   sage -f python2
>   sage -i pyopenssl
>
>

-- 
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] making database_gap (starting from GAP 4.9) standard - please vote

[David Joyner]

On Feb 17, 2018 6:01 PM, "Dima Pasechnik"  wrote:

GAP 4.9 (a release candidate, released 1st Feb) has  smallgrps and
transgrps, two GAP packages/libraries which are extremely useful, with
GPL-compatible licenses. In the past (and up to current GAP 4.8)
they had licenses non-GPL compatible licenses, preventing them from being
made standard.

It's about 60MB extra, but it would really make it possible to distribute
an essentially standard configuration of GAP, reducing the chances of
various mishaps, and easing the support a lot.

Thus I'm calling for a vote on this: to make database_gap standard as soon
as license permits (i.e. as soon as we update to GAP 4.9).


+1


Dima



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

Re: [sage-devel] making database_gap (starting from GAP 4.9) standard - please vote

[Dima Pasechnik]

On Saturday, February 17, 2018 at 11:05:49 PM UTC, François Bissey wrote:
>
>
>
> > On 18/02/2018, at 12:01, Dima Pasechnik  
> wrote: 
> > 
> > GAP 4.9 (a release candidate, released 1st Feb) has  smallgrps and 
> transgrps, two GAP packages/libraries which are extremely useful, with 
> GPL-compatible licenses. In the past (and up to current GAP 4.8) 
> > they had licenses non-GPL compatible licenses, preventing them from 
> being made standard. 
> > 
> > It's about 60MB extra, but it would really make it possible to 
> distribute an essentially standard configuration of GAP, reducing the 
> chances of various mishaps, and easing the support a lot. 
> > 
> > Thus I'm calling for a vote on this: to make database_gap standard as 
> soon as license permits (i.e. as soon as we update to GAP 4.9). 
> > 
>
> I am all for including those database as standard ASAP. 
>
> However currently it is put in a separate package from the main gap 
> spkg by sage devs. So rather than making database_gap standard I say 
> just stop splitting it from the main gap install. 
>
>
well, yes --- but this is more of a detail. No vote is needed to merge 
standard packages, I suppose.
 

> 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] making database_gap (starting from GAP 4.9) standard - please vote

[François Bissey]

> On 18/02/2018, at 12:01, Dima Pasechnik  wrote:
> 
> GAP 4.9 (a release candidate, released 1st Feb) has  smallgrps and transgrps, 
> two GAP packages/libraries which are extremely useful, with GPL-compatible 
> licenses. In the past (and up to current GAP 4.8)
> they had licenses non-GPL compatible licenses, preventing them from being 
> made standard.
> 
> It's about 60MB extra, but it would really make it possible to distribute an 
> essentially standard configuration of GAP, reducing the chances of various 
> mishaps, and easing the support a lot.
> 
> Thus I'm calling for a vote on this: to make database_gap standard as soon as 
> license permits (i.e. as soon as we update to GAP 4.9).
> 

I am all for including those database as standard ASAP.

However currently it is put in a separate package from the main gap
spkg by sage devs. So rather than making database_gap standard I say
just stop splitting it from the main gap install.

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.

[sage-devel] making database_gap (starting from GAP 4.9) standard - please vote

[Dima Pasechnik]

GAP 4.9 (a release candidate, released 1st Feb) has  smallgrps and 
transgrps, two GAP packages/libraries which are extremely useful, with 
GPL-compatible licenses. In the past (and up to current GAP 4.8)
they had licenses non-GPL compatible licenses, preventing them from being 
made standard.

It's about 60MB extra, but it would really make it possible to distribute 
an essentially standard configuration of GAP, reducing the chances of 
various mishaps, and easing the support a lot.

Thus I'm calling for a vote on this: to make database_gap standard as soon 
as license permits (i.e. as soon as we update to GAP 4.9).

Dima

 

-- 
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: Sage 8.1 eats memory while 7.5.1 did not

[Samuel Lelievre]

Sat 2018-02-17 07:38:20 UTC, Ralf Stephan:
>
> On Friday, February 16, 2018 at 10:05:02 AM UTC+1, Dima Pasechnik wrote:
>>
>> guppy.hpy() finds 149 objects 
>> dict of sympy.core.assumptions.ManagedProperties
>> on the heap
>
> The solution of the original issue did not involve sympy so I was trying 
to reproduce this, but when trying to SAGE_ROOT/local/bin/pip install guppy 
I got
>
> pip is configured with locations that require TLS/SSL, however the ssl 
module in Python is not available.
> Collecting guppy
>   Could not fetch URL https://pypi.python.org/simple/guppy/: There was a 
problem confirming the ssl certificate: Can't connect to HTTPS URL because 
the SSL module is not available. - skipping
>   Could not find a version that satisfies the requirement guppy (from 
versions: )
> No matching distribution found for guppy
>
> How did you install guppy?

Installing extra packages with Sage's pip as in

sage --pip install guppy

will only succeed if Sage's Python has ssl support.

For this to be the case, you need one of the following:

- have system-wide ssl support before building Sage.
  In Ubuntu, this would be achieved by running

  sudo apt full-upgrade
  sudo apt install openssl libssl-dev

- install ssl support before building Sage:

  ./sage -i openssl
  make

- install ssl support once Sage is already built:

  sage -i openssl
  sage -f python2
  sage -i pyopenssl

-- 
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: Errors in GAP small groups library

[Dima Pasechnik]

On Saturday, February 17, 2018 at 11:53:51 AM UTC, Simon King wrote:
>
> Hi! 
>
> On 2018-02-17, Dima Pasechnik  wrote: 
> > sage: gap_reset_workspace(verbose=True) 
>
> Doing that, I get 
>  sage: gap_reset_workspace(verbose=True) 
>  Loading GAP package GAPDoc 
>  Loading GAP package ctbllib 
>  Loading GAP package sonata 
>  Loading GAP package guava 
>  Loading GAP package factint 
>  Loading GAP package gapdoc 
>  Loading GAP package grape 
>  Loading GAP package design 
>  Loading GAP package toric 
>  Loading GAP package laguna 
>  Loading GAP package braid 
>  *** Error loading Gap package braid. You may want to install the 
>  gap_packages and/or database_gap SPKGs. 
>
> The punchline is that I installed both gap_packages and database_gap! 
>
> Also 
>  sage: gap.eval('LoadPackage("CRISP");') 
>  'fail' 
> Is CRISP supposed to be part of database_gap? 
>
 
no. Sage never packaged CRISP.
CRISP can be easily installed as an extra GAP package directly into 
SAGE_LOCAL/gap/latest/pkg/
as it does not need any compilation, it's all pure GAP code.

There isn't much to fix. 

The GAP situation is somehow unfortunate, as upstream promised to provide a 
replacement for libGAP
some time ago, but this still has to happen...
 

>
> So, how to fix all that? 
>
> Best regards, 
> Simon 
>
>

-- 
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: Errors in GAP small groups library

[Simon King]

Hi!

On 2018-02-17, Dima Pasechnik  wrote:
> sage: gap_reset_workspace(verbose=True)

Doing that, I get
 sage: gap_reset_workspace(verbose=True)
 Loading GAP package GAPDoc
 Loading GAP package ctbllib
 Loading GAP package sonata
 Loading GAP package guava
 Loading GAP package factint
 Loading GAP package gapdoc
 Loading GAP package grape
 Loading GAP package design
 Loading GAP package toric
 Loading GAP package laguna
 Loading GAP package braid
 *** Error loading Gap package braid. You may want to install the
 gap_packages and/or database_gap SPKGs.

The punchline is that I installed both gap_packages and database_gap!

Also
 sage: gap.eval('LoadPackage("CRISP");')
 'fail'
Is CRISP supposed to be part of database_gap?

So, how to fix all that?

Best regards,
Simon

-- 
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] Re: Errors in GAP small groups library

[Dima Pasechnik]

I can further add that GAP 4.9 fixes this: for 
computing NormalSubgroups(SmallGroup(1458,1180));
CRISP is no longer neeed.


On Saturday, February 17, 2018 at 10:30:01 AM UTC, Dima Pasechnik wrote:
>
>
>
> On Saturday, February 17, 2018 at 7:31:19 AM UTC, David Roe wrote:
>>
>> I realized that I ran
>> sage: gap.eval('LoadAllPackages();')
>> which broke libgap.  
>>
>
> Really? I don't think so. It didn't break it for me, although it did break 
> GAP's workspaces, which is for some reason very fragile.
> (libGAP and GAP have separate workspaces in Sage)
> What happened is the following, I think: copying the packages from GAP 
> source broke some GAP packages in Sage's
> GAP pkg/ directory, namely at least sonata (mea culpa, I should have 
> warned you about it)
>
> sage: gap_reset_workspace(verbose=True)
> Loading GAP package GAPDoc
> Loading GAP package ctbllib
> Loading GAP package sonata
> Warning: this should never happen
>
> (and Sage hangs)
>
> In fact, this is coming from 
>
> elif x==13: #@w GAP is trying to send a Window command
>
> in src/sage/interfaces/gap.py
> I have no clue what "Window command" is. Anyway, the error message should 
> not be identical to the one from
>
>elif x==12: #@sN shouldn't happen
>
> I also don't know the reason for that "Window command" --- is it cause it 
> is meant to print some info message?
>
>   
>
>> For anyone else reading this, the following fixed the problem (taken from 
>> gap_reset_workspace, with sonata and guava removed due to "Warning: this 
>> should never happen" and braid removed because I don't have it installed):
>>
>> g = Gap(use_workspace_cache=False, max_workspace_size=None)
>> g.eval('SetUserPreference("HistoryMaxLines", 30)')
>> for pkg in ['GAPDoc', 'ctbllib', 'factint', 'gapdoc', 'grape', 'design', 
>> 'toric', 'laguna']:
>> g.load_package(pkg, verbose=True)
>> g.save_workspace()
>> g.quit()
>>
>> Thanks for the help Dima: my calculations are running smoothly again!
>> David
>>
>> On Sat, Feb 17, 2018 at 12:57 AM, David Roe  wrote:
>>
>>> Thanks, that helps a lot.  After some experimentation, it seems like
>>> gap> LoadPackage("CRISP");
>>> is sufficient.
>>>
>>> However, when I try to do it from sage I get the following:
>>> sage: gap.eval('LoadPackage("CRISP");')
>>> Warning: this should never happen
>>>
>>> and sage hangs.  Googling leads me to 
>>> https://groups.google.com/forum/#!topic/sage-support/60HHHL8Bw_8, which 
>>> I interpret as suggesting that CRISP is using LoadDynamicModule. However, 
>>> searching on https://github.com/bh11/crisp, I don't see any calls to 
>>> that function.  Is there something else that could be responsible?  Is 
>>> there a way to use CRISP through gap.eval in Sage?
>>> David
>>>
>>> On Fri, Feb 16, 2018 at 11:40 PM, Dima Pasechnik  
>>> wrote:
>>>
 The problem is in the packages loaded (or not) by Sage's GAP vs by 
 GAP's GAP.
 Namely, if I start Sage's gap by ./sage --gap
 and do
 gap> LoadAllPackages();
 gap> NormalSubgroups(SmallGroup(1458,1180));
 I'd get your error

 Now, if I take GAP's source for 4.8.6:

 https://www.gap-system.org/pub/gap/gap48/tar.bz2/gap4r8p6_2016_11_12-14_25.tar.bz2
 untar it, and copy its pkg/ directory to $SAGEROOT/local/gap/latest/
  start Sage's gap by ./sage --gap
 and do
 gap> LoadAllPackages();
 gap> NormalSubgroups(SmallGroup(1458,1180));
 [ , Group([ f1, f2, f3^2*f4, 
 f5, f6, f7 ]), Group([ f2, f3^2*f4, f4, f5, f6, f7 ]), 
   Group([ f1, f3^2*f4, f4, f5, f6, f7 ]), Group([ f1, f2*f4*f6, 
 f3^2*f4, f5, f6, f7 ]), Group([ f1, f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), 
   Group([ f1, f3^2*f4, f5, f6, f7 ]), Group([ f3^2*f4, f4, f5, f6, f7 
 ]), Group([ f2*f4*f6, f3^2*f4, f5, f6, f7 ]), 
   Group([ f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), Group([ f2, f3^2*f4, 
 f5, f6, f7 ]), Group([ f1, f3^2*f4, f5*f6^2, f7 ]), Group([ f3^2*f4, f5, 
 f6, f7 ]), 
   Group([ f2*f3^2*f4, f3^2*f4^2, f5*f6^2, f6, f7 ]), Group([ f3^2*f4^2, 
 f5*f6^2, f6, f7 ]), Group([ f2*f3*f6*f7, f5*f6^2, f6, f7 ]), 
   Group([ f2^2*f4*f6^2, f5*f6^2, f6, f7 ]), Group([ f2*f3^2*f4, 
 f5*f6^2, f6, f7 ]), Group([ f5*f6^2, f6, f7 ]), Group([ f3^2*f4, f5*f6^2, 
 f7 ]), 
   Group([ f3^2*f4^2, f5^2*f6^2, f7 ]), Group([ f5^2*f6^2, f7 ]), 
 Group([ f5*f6^2, f7 ]), Group([ f7 ]), Group([  ]) ]

 --- it works.
 Note that LoadAllPackages() is necessary, as apparently the GAP code 
 uses one of these packages for these
 computation without telling us.

 So this is a sort of bug, yes, in our way of packaging GAP packages 
 (and it's a sort of GAP's bug to call a code from a package
 without loading it explicitly...)
 I don't know what package it is yet.
 It's very early Sat. morning here, I'll have a look at it over the 
 weekend.
  

 On Saturday, February 17, 2018 at 3:12:25 AM UTC, David Roe 

[sage-devel] Re: Sage 8.1 eats memory while 7.5.1 did not

[Dima Pasechnik]

On Saturday, February 17, 2018 at 7:38:20 AM UTC, Ralf Stephan wrote:
>
> On Friday, February 16, 2018 at 10:05:02 AM UTC+1, Dima Pasechnik wrote:
>>
>> guppy.hpy() finds 149 objects 
>> dict of sympy.core.assumptions.ManagedProperties
>> on the heap
>>
>
> The solution of the original issue did not involve sympy so I was trying 
> to reproduce this, but when trying to SAGE_ROOT/local/bin/pip install guppy 
> I got
>
> pip is configured with locations that require TLS/SSL, however the ssl 
> module in Python is not available.
> Collecting guppy
>   Could not fetch URL https://pypi.python.org/simple/guppy/: There was a 
> problem confirming the ssl certificate: Can't connect to HTTPS URL because 
> the SSL module is not available. - skipping
>   Could not find a version that satisfies the requirement guppy (from 
> versions: )
> No matching distribution found for guppy
>
> How did you install guppy?
>

I ran ./sage --pip install guppy

Anyhow, it seems that my guess about a leak in sympy is wrong.
These sympy.core.assumptions.ManagedProperties is something one gets by
importing sympy (or one of its components)


-- 
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] Re: Errors in GAP small groups library

[Dima Pasechnik]

On Saturday, February 17, 2018 at 7:31:19 AM UTC, David Roe wrote:
>
> I realized that I ran
> sage: gap.eval('LoadAllPackages();')
> which broke libgap.  
>

Really? I don't think so. It didn't break it for me, although it did break 
GAP's workspaces, which is for some reason very fragile.
(libGAP and GAP have separate workspaces in Sage)
What happened is the following, I think: copying the packages from GAP 
source broke some GAP packages in Sage's
GAP pkg/ directory, namely at least sonata (mea culpa, I should have warned 
you about it)

sage: gap_reset_workspace(verbose=True)
Loading GAP package GAPDoc
Loading GAP package ctbllib
Loading GAP package sonata
Warning: this should never happen

(and Sage hangs)

In fact, this is coming from 

elif x==13: #@w GAP is trying to send a Window command

in src/sage/interfaces/gap.py
I have no clue what "Window command" is. Anyway, the error message should 
not be identical to the one from

   elif x==12: #@sN shouldn't happen

I also don't know the reason for that "Window command" --- is it cause it 
is meant to print some info message?

  

> For anyone else reading this, the following fixed the problem (taken from 
> gap_reset_workspace, with sonata and guava removed due to "Warning: this 
> should never happen" and braid removed because I don't have it installed):
>
> g = Gap(use_workspace_cache=False, max_workspace_size=None)
> g.eval('SetUserPreference("HistoryMaxLines", 30)')
> for pkg in ['GAPDoc', 'ctbllib', 'factint', 'gapdoc', 'grape', 'design', 
> 'toric', 'laguna']:
> g.load_package(pkg, verbose=True)
> g.save_workspace()
> g.quit()
>
> Thanks for the help Dima: my calculations are running smoothly again!
> David
>
> On Sat, Feb 17, 2018 at 12:57 AM, David Roe  > wrote:
>
>> Thanks, that helps a lot.  After some experimentation, it seems like
>> gap> LoadPackage("CRISP");
>> is sufficient.
>>
>> However, when I try to do it from sage I get the following:
>> sage: gap.eval('LoadPackage("CRISP");')
>> Warning: this should never happen
>>
>> and sage hangs.  Googling leads me to 
>> https://groups.google.com/forum/#!topic/sage-support/60HHHL8Bw_8, which 
>> I interpret as suggesting that CRISP is using LoadDynamicModule. However, 
>> searching on https://github.com/bh11/crisp, I don't see any calls to 
>> that function.  Is there something else that could be responsible?  Is 
>> there a way to use CRISP through gap.eval in Sage?
>> David
>>
>> On Fri, Feb 16, 2018 at 11:40 PM, Dima Pasechnik > > wrote:
>>
>>> The problem is in the packages loaded (or not) by Sage's GAP vs by GAP's 
>>> GAP.
>>> Namely, if I start Sage's gap by ./sage --gap
>>> and do
>>> gap> LoadAllPackages();
>>> gap> NormalSubgroups(SmallGroup(1458,1180));
>>> I'd get your error
>>>
>>> Now, if I take GAP's source for 4.8.6:
>>>
>>> https://www.gap-system.org/pub/gap/gap48/tar.bz2/gap4r8p6_2016_11_12-14_25.tar.bz2
>>> untar it, and copy its pkg/ directory to $SAGEROOT/local/gap/latest/
>>>  start Sage's gap by ./sage --gap
>>> and do
>>> gap> LoadAllPackages();
>>> gap> NormalSubgroups(SmallGroup(1458,1180));
>>> [ , Group([ f1, f2, f3^2*f4, 
>>> f5, f6, f7 ]), Group([ f2, f3^2*f4, f4, f5, f6, f7 ]), 
>>>   Group([ f1, f3^2*f4, f4, f5, f6, f7 ]), Group([ f1, f2*f4*f6, f3^2*f4, 
>>> f5, f6, f7 ]), Group([ f1, f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), 
>>>   Group([ f1, f3^2*f4, f5, f6, f7 ]), Group([ f3^2*f4, f4, f5, f6, f7 
>>> ]), Group([ f2*f4*f6, f3^2*f4, f5, f6, f7 ]), 
>>>   Group([ f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), Group([ f2, f3^2*f4, f5, 
>>> f6, f7 ]), Group([ f1, f3^2*f4, f5*f6^2, f7 ]), Group([ f3^2*f4, f5, f6, f7 
>>> ]), 
>>>   Group([ f2*f3^2*f4, f3^2*f4^2, f5*f6^2, f6, f7 ]), Group([ f3^2*f4^2, 
>>> f5*f6^2, f6, f7 ]), Group([ f2*f3*f6*f7, f5*f6^2, f6, f7 ]), 
>>>   Group([ f2^2*f4*f6^2, f5*f6^2, f6, f7 ]), Group([ f2*f3^2*f4, f5*f6^2, 
>>> f6, f7 ]), Group([ f5*f6^2, f6, f7 ]), Group([ f3^2*f4, f5*f6^2, f7 ]), 
>>>   Group([ f3^2*f4^2, f5^2*f6^2, f7 ]), Group([ f5^2*f6^2, f7 ]), Group([ 
>>> f5*f6^2, f7 ]), Group([ f7 ]), Group([  ]) ]
>>>
>>> --- it works.
>>> Note that LoadAllPackages() is necessary, as apparently the GAP code 
>>> uses one of these packages for these
>>> computation without telling us.
>>>
>>> So this is a sort of bug, yes, in our way of packaging GAP packages (and 
>>> it's a sort of GAP's bug to call a code from a package
>>> without loading it explicitly...)
>>> I don't know what package it is yet.
>>> It's very early Sat. morning here, I'll have a look at it over the 
>>> weekend.
>>>  
>>>
>>> On Saturday, February 17, 2018 at 3:12:25 AM UTC, David Roe wrote:

 I'm trying to use GAP's small groups library (after installing 
 gap_packages) and getting strange errors that don't occur in GAP when 
 built 
 from source.  In particular (using gap_console to get more traceback)

 sage: gap_console()
 ...
 gap> NormalSubgroups(SmallGroup(1458,1180));
 Error, 

Re: [sage-devel] Possibly bug in factoring over Cyclotomic fields

[Robert Pollack]

Thanks David.  I just reported the bug to PARI.

Rob

On Sat, Feb 17, 2018 at 10:04 AM, David Loeffler  wrote:

> This is a bug in PARI, rather than in Sage, apparently:
>
>   GP/PARI CALCULATOR Version 2.9.4 (released)
>
>   amd64 running linux (x86-64/GMP-6.1.0 kernel) 64-bit version
>
> [...]
>
> ? nffactor(y^8 - y^6 + y^4 - y^2 + 1, x^4 + 1) \\ works
>
> %1 =
>
> [x^2 + Mod(-y^5, y^8 - y^6 + y^4 - y^2 + 1) 1]
>
>
> [ x^2 + Mod(y^5, y^8 - y^6 + y^4 - y^2 + 1) 1]
>
>
> ? nffactor(y^8 - y^6 + y^4 - y^2 + 1, x^4 - 1) \\ boom
>
>   ***   at top-level: nffactor(y^8-y^6+y^4
>
>   *** ^
>
>   *** nffactor: inconsistent concatenation t_VEC (2 elts) , t_COL (2
> elts).
>
>   ***   Break loop: type 'break' to go back to GP prompt
>
>
>
> On 16 February 2018 at 16:54,  wrote:
>
>> The following code crashes (in Sage 8.1 and on CoCalc):
>>
>> sage: K=CyclotomicField(20)
>> sage: R.=PolynomialRing(K)
>> sage: (x^4-1).factor()
>> 
>> ---
>> PariError Traceback (most re
>> cent call last)
>>  in ()
>> > 1 (x**Integer(4)-Integer(1)).factor()
>>
>> /ext/sage/sage-8.1/src/sage/rings/polynomial/polynomial_element.pyx in
>> sage.rings.polynomial.polynomial_element.Polynomi
>> al.factor (build/cythonized/sage/rings/polynomi
>> al/polynomial_element.c:39428)()
>>4127 # polynomial instead.
>>4128 Rpari = R.pari_polynomial("y")
>> -> 4129 G = list(Rpari.nffactor(f))
>>4130 # PARI's nffactor() ignores the unit, _f
>> actor_pari_helper()
>>4131 # adds back the unit of the factorization.
>>
>> cypari2/auto_gen.pxi in cypari2.gen.Gen_auto.nffactor()
>>
>> cypari2/handle_error.pyx in cypari2.handle_error._pari_err_handle()
>>
>> PariError: inconsistent concatenation t_VEC (2 elts) , t_COL (2 elts)
>>
>> --
>> 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 a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-devel/elFDJxE-9qA/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

Re: [sage-devel] [Crypto] S-box Linear Approximation Matrix scaling

[Friedrich Wiemer]

Ah, thats a very good idea!
Then I would suggest to extend this scaled argument to the following:

"bias" - return actual biases that is in [-0.5, 0.5]
"correlation" - return correlations, so in [-1, 1]
"absolute bias" - return biases*2^n (default)
"fourier coefficient" - return fourier coefficients, in [-2^n, 2^n]

With this, I guess, the doc-string can also be improved to make the default 
behavior clearer.

-- 
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] Re: Errors in GAP small groups library

[Dima Pasechnik]

On Saturday, February 17, 2018 at 5:58:17 AM UTC, David Roe wrote:
>
> Thanks, that helps a lot.  After some experimentation, it seems like
> gap> LoadPackage("CRISP");
> is sufficient.
>

Indeed, thanks for digging this up.
 

>
> However, when I try to do it from sage I get the following:
> sage: gap.eval('LoadPackage("CRISP");')
> Warning: this should never happen
>

this is some kind of pexpect interface problem, I gather, related to Tab 
completion.
I get this if I just hit Tab
at
sage: gap. 

I guess it's the same kind of issue 
as https://trac.sagemath.org/ticket/22766 and
https://trac.sagemath.org/ticket/23956 (a gift from Ipython, which in its 
current 
Sage version does multithreaded tab completion, causing havoc with packages 
that do non-trivial
things at Tab completion

At least the following works:

sage: libgap.LoadPackage("CRISP")
true
sage: libgap.SmallGroup(1458,1180)

sage: s=libgap.SmallGroup(1458,1180); s

sage: libgap.NormalSubgroups(s)
[ , Group([ f1, f2, f3^2*f4, f5, 
f6, f7 ]), Group([ f2, f3^2*f4, f4, f5, f6, f7 ]), Group([ f1, f3^2*f4, f4, 
f5, f6, f7 ]), Group([ f1, f2*f4*f6, f3^2*f4, f5, f6, f7 ]), Group([ f1, 
f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), Group([ f1, f3^2*f4, f5, f6, f7 ]), 
Group([ f3^2*f4, f4, f5, f6, f7 ]), Group([ f2*f4*f6, f3^2*f4, f5, f6, f7 
]), Group([ f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), Group([ f2, f3^2*f4, f5, 
f6, f7 ]), Group([ f2*f3^2*f4, f3^2*f4^2, f5, f6, f7 ]), Group([ f3^2*f4^2, 
f5, f6, f7 ]), Group([ f2*f3*f6*f7, f5, f6, f7 ]), Group([ f2^2*f4*f6^2, 
f5, f6, f7 ]), Group([ f2*f3^2*f4, f5, f6, f7 ]), Group([ f3^2*f4, f5, f6, 
f7 ]), Group([ f3^2*f4^2, f5*f6, f7 ]), Group([ f5, f6, f7 ]), Group([ f1, 
f3^2*f4, f5*f6^2, f7 ]), Group([ f3^2*f4, f5*f6^2, f7 ]), Group([ f5*f6^2, 
f7 ]), Group([ f5*f6, f7 ]), Group([ f7 ]), Group([  ]) ]


> and sage hangs.  Googling leads me to 
> https://groups.google.com/forum/#!topic/sage-support/60HHHL8Bw_8, which I 
> interpret as suggesting that CRISP is using LoadDynamicModule. However, 
> searching on https://github.com/bh11/crisp, I don't see any calls to that 
> function.  Is there something else that could be responsible?  Is there a 
> way to use CRISP through gap.eval in Sage?
>

use libgap, it works :-)
 

> David
>
> On Fri, Feb 16, 2018 at 11:40 PM, Dima Pasechnik  > wrote:
>
>> The problem is in the packages loaded (or not) by Sage's GAP vs by GAP's 
>> GAP.
>> Namely, if I start Sage's gap by ./sage --gap
>> and do
>> gap> LoadAllPackages();
>> gap> NormalSubgroups(SmallGroup(1458,1180));
>> I'd get your error
>>
>> Now, if I take GAP's source for 4.8.6:
>>
>> https://www.gap-system.org/pub/gap/gap48/tar.bz2/gap4r8p6_2016_11_12-14_25.tar.bz2
>> untar it, and copy its pkg/ directory to $SAGEROOT/local/gap/latest/
>>  start Sage's gap by ./sage --gap
>> and do
>> gap> LoadAllPackages();
>> gap> NormalSubgroups(SmallGroup(1458,1180));
>> [ , Group([ f1, f2, f3^2*f4, f5, 
>> f6, f7 ]), Group([ f2, f3^2*f4, f4, f5, f6, f7 ]), 
>>   Group([ f1, f3^2*f4, f4, f5, f6, f7 ]), Group([ f1, f2*f4*f6, f3^2*f4, 
>> f5, f6, f7 ]), Group([ f1, f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), 
>>   Group([ f1, f3^2*f4, f5, f6, f7 ]), Group([ f3^2*f4, f4, f5, f6, f7 ]), 
>> Group([ f2*f4*f6, f3^2*f4, f5, f6, f7 ]), 
>>   Group([ f2^2*f4*f6^2, f3^2*f4, f5, f6, f7 ]), Group([ f2, f3^2*f4, f5, 
>> f6, f7 ]), Group([ f1, f3^2*f4, f5*f6^2, f7 ]), Group([ f3^2*f4, f5, f6, f7 
>> ]), 
>>   Group([ f2*f3^2*f4, f3^2*f4^2, f5*f6^2, f6, f7 ]), Group([ f3^2*f4^2, 
>> f5*f6^2, f6, f7 ]), Group([ f2*f3*f6*f7, f5*f6^2, f6, f7 ]), 
>>   Group([ f2^2*f4*f6^2, f5*f6^2, f6, f7 ]), Group([ f2*f3^2*f4, f5*f6^2, 
>> f6, f7 ]), Group([ f5*f6^2, f6, f7 ]), Group([ f3^2*f4, f5*f6^2, f7 ]), 
>>   Group([ f3^2*f4^2, f5^2*f6^2, f7 ]), Group([ f5^2*f6^2, f7 ]), Group([ 
>> f5*f6^2, f7 ]), Group([ f7 ]), Group([  ]) ]
>>
>> --- it works.
>> Note that LoadAllPackages() is necessary, as apparently the GAP code uses 
>> one of these packages for these
>> computation without telling us.
>>
>> So this is a sort of bug, yes, in our way of packaging GAP packages (and 
>> it's a sort of GAP's bug to call a code from a package
>> without loading it explicitly...)
>> I don't know what package it is yet.
>> It's very early Sat. morning here, I'll have a look at it over the 
>> weekend.
>>  
>>
>> On Saturday, February 17, 2018 at 3:12:25 AM UTC, David Roe wrote:
>>>
>>> I'm trying to use GAP's small groups library (after installing 
>>> gap_packages) and getting strange errors that don't occur in GAP when built 
>>> from source.  In particular (using gap_console to get more traceback)
>>>
>>> sage: gap_console()
>>> ...
>>> gap> NormalSubgroups(SmallGroup(1458,1180));
>>> Error, List Element: [4] must have an assigned value in
>>>   if map[d] > max  then
>>> elm := id;
>>> else
>>> if not IsBound( map[d] )  then
>>> Error( " lies not in group defined by " );
>>> fi;
>>> ll := LeadingExponentOfPcElement( pa, elm );
>>> lr 

Re: [sage-devel] Possibly bug in factoring over Cyclotomic fields

[David Loeffler]

This is a bug in PARI, rather than in Sage, apparently:

  GP/PARI CALCULATOR Version 2.9.4 (released)

  amd64 running linux (x86-64/GMP-6.1.0 kernel) 64-bit version

[...]

? nffactor(y^8 - y^6 + y^4 - y^2 + 1, x^4 + 1) \\ works

%1 =

[x^2 + Mod(-y^5, y^8 - y^6 + y^4 - y^2 + 1) 1]


[ x^2 + Mod(y^5, y^8 - y^6 + y^4 - y^2 + 1) 1]


? nffactor(y^8 - y^6 + y^4 - y^2 + 1, x^4 - 1) \\ boom

  ***   at top-level: nffactor(y^8-y^6+y^4

  *** ^

  *** nffactor: inconsistent concatenation t_VEC (2 elts) , t_COL (2 elts).

  ***   Break loop: type 'break' to go back to GP prompt



On 16 February 2018 at 16:54,  wrote:

> The following code crashes (in Sage 8.1 and on CoCalc):
>
> sage: K=CyclotomicField(20)
> sage: R.=PolynomialRing(K)
> sage: (x^4-1).factor()
> 
> ---
> PariError Traceback (most
> recent call last)
>  in ()
> > 1 (x**Integer(4)-Integer(1)).factor()
>
> /ext/sage/sage-8.1/src/sage/rings/polynomial/polynomial_element.pyx in
> sage.rings.polynomial.polynomial_element.Polynomial.factor (build/
> cythonized/sage/rings/polynomi
> al/polynomial_element.c:39428)()
>4127 # polynomial instead.
>4128 Rpari = R.pari_polynomial("y")
> -> 4129 G = list(Rpari.nffactor(f))
>4130 # PARI's nffactor() ignores the unit, _
> factor_pari_helper()
>4131 # adds back the unit of the factorization.
>
> cypari2/auto_gen.pxi in cypari2.gen.Gen_auto.nffactor()
>
> cypari2/handle_error.pyx in cypari2.handle_error._pari_err_handle()
>
> PariError: inconsistent concatenation t_VEC (2 elts) , t_COL (2 elts)
>
> --
> 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.