Re: [sage-devel] Re: Database of number fields

['Julien Puydt' via sage-devel]

Le samedi 22 février 2020 à 18:36 -0800, Nils Bruin a écrit :
> On Saturday, February 22, 2020 at 12:54:47 PM UTC-8, Snark wrote:
> > If I understand well, there's a series of build steps : 
> >   pari code -> data files -> sobj 
> > and the last step is jones.py. 
> > 
> 
> As far as you, the software packager, are concerned, the only
> relevant step just data files -> sobj. "jones.py" actually gives you
> the means of doing that conversion. It's indeed a little vague from
> which data files the current "sobj" was constructed. That probably
> means you get to pick!.

Not really : as the software packager in Debian, I'm supposed to use
sources, so I am supposed to start from the initial computing scripts,
turn them into data files and then into sobj.

Being vague about what the sources are when the package is under GPL is
a concept I'm a bit uncomfortable with.

> Constructing the original data files earned the authors a scientific
> publication. Replicability is nice, but I don't think it's required
> to be explicitly performed every time software is packaged/installed
> (and indeed, it may have cost significant CPU cycles, even if the gp
> program used for it is tiny).

If the initial computing scripts take very long, then as an exception,
I'll ship the data files and build from them. But I'll still ship the
initial computing scripts so anyone with enough computing power
can replicate! [The Debian build hosts stop compilations after 150min
of log-inactivity, for example.]

The size of gp doesn't matter : my package would just build-depend, but
not depend on it.

> I don't think there's going to be any versioning. Once you've
> tabulated all the quintic number fields unramified outside {2,3,5,7},
> there's very little that's going change anymore about it (although
> people could discover errors in your tabulation ...).

Well, I'll version on the day I got the data files then. Or the
computing scripts.

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/28c78e125ced6ff43b54ee265c6141f3fd540ed9.camel%40laposte.net.

Re: [sage-devel] Re: Database of number fields

['Julien Puydt' via sage-devel]

Hi,


Le samedi 22 février 2020 à 09:33 -0800, Nils Bruin a écrit :
> Sorry, code to produce the sobj is already included in the package.
> From jones.py:

> def _init(self, path):
> """
> Create the database from scratch from the PARI files on John
> Jones's
> web page, downloaded (e.g., via wget) to a local directory,
> which
> is specified as path above.
> 
> INPUT:
> 
> 
> -  ``path`` - (default works on William Stein install.)
>path must be the path to Jones's Number_Fields directory
>http://hobbes.la.asu.edu/Number_Fields These files should
> have
>been downloaded using wget.
> 
> 
> EXAMPLES: This is how to create the database from scratch,
> assuming
> that the number fields are in the default directory above:
> From a
> cold start of Sage::
> 
> sage: J = JonesDatabase()
> sage: J._init()   # not tested
> ...
> 
> This takes about 5 seconds.
> """
> from sage.misc.misc import sage_makedirs
> x = PolynomialRing(RationalField(), 'x').gen()
> self.root = {}
> self.root[tuple([])] = [x - 1]
> if not os.path.exists(path):
> raise IOError("Path %s does not exist." % path)
> for X in os.listdir(path):
> if X[-4:] == "solo":
> Z = path + "/" + X
> print(X)
> for Y in os.listdir(Z):
> if Y[-3:] == ".gp":
> self._load(Z, Y)
> sage_makedirs(JONESDATA)
> save(self.root, JONESDATA + "/jones.sobj")
> 
> Modulo collecting the text source that aren't included (but readily
> available on a web site), the code to compile the database is already
> there! You might want to check with the author if he/she is OK with
> you downloading and distributing the text files separately, but for
> robustness I think you'd be doing the community a favour by wrapping
> the data in a "source distribution" too.

If I understand well, there's a series of build steps :
  pari code -> data files -> sobj
and the last step is jones.py.

But then what I want is the pari code, as that's the source.

(Unless computing the data files is incredibly long, in which case I'll
ship both the pari code and the data files, with a nice notice to
explain that I ship pre-build for a good reason.)

It's not clear which data files have been used to generate the current
sagemath package : https://hobbes.la.asu.edu/Number_Fields/ points to
several pages (including a 404), and on each of these pages, there's a
link to .gp files which must be the ones getting used, if I understand
well.

And how is versioning managed?

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f36e52ce492d702904f9817f6c227da4e0ff546b.camel%40laposte.net.

[sage-devel] Database of number fields

['Julien Puydt' via sage-devel]

Hi,

I wanted to package sagemath's optional package
"database_jones_numfield" for Debian, but it appears to be merely a
binary object.

For Debian, I need sources : where is the generation script I can use
to re-generate the .sobj?

Thanks,

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/77bac9a3e88478d2567400867a739535f3dc27c0.camel%40laposte.net.

Re: [sage-devel] Python 2->3 incompatibility in unpickling

['Julien Puydt' via sage-devel]

Le mercredi 22 janvier 2020 à 21:35 +, Simon King a écrit :
> Consequently, when unpickling my old data with Python-3, I want the
> Python-2 str to be interpreted as bytes. However, Python-3 insists on
> misinterpreting it as str, and I have trouble to turn that str into
> an appropriate bytes.

Did you try forcing the pickling "protocol" parameter ?

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3bc5a1f8b524d8315c124f498b8497fd93550862.camel%40laposte.net.

Re: [sage-devel] Re: Unpickling problem (backwards incompatibility) in Python 3

['Julien Puydt' via sage-devel]

Hi,
Le 02/09/2019 à 22:43, Simon King a écrit :
> AFAIK, what I need to unpickle my old data is a way to tell Python-3
> that it shall (at least temporarily) unpickle all strings as bytes, in
> the sense that the pickled string  '\x80\x1f' should be understood as
> b'\x80\x1f'. Is there a way?

I tried to run the following two small scripts, and it didn't complain:


#!/usr/bin/python2

import pickle

s='\x80\x1f'
with open('/tmp/data.pickle', 'w') as handle:
pickle.dump(s, handle, protocol=2)





#!/usr/bin/python3

import pickle

with open('/tmp/data.pickle', 'rb') as handle:
s = pickle.load(handle, encoding='bytes')



I hope that helps,

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4347937a-bd99-b854-cf90-6bc0bb394358%40laposte.net.

Re: [sage-devel] Cremona's database of elliptic curves over rationals : compilation?

['Julien Puydt' via sage-devel]

Hi,

Le 21/08/2019 à 13:43, John Cremona a écrit :
> I suggest that you ship the whole thing so that a debian (or derivative)
> user who installs the package gets everything they could also get by
> either git-cloning the ecdata repository (but without the git history)
> or the tarball from github.

Well, my source package has files, but the binary only has the .db file,
so I don't have much motivation to ship a complete source...

There's also the fact that I only need good copyright+license
assignments on files in the source package - so cutting down on it is
interesting.

> It would be quite possible for the Sage interface to extract more of the
> data than it does.  Since William and I first set up this spkg in about
> 2006 the extent of the data stored in ecdata has grown -- not only the
> number for curves, also more date with each curve.   For example:  the
> integral points on each curve.  I do not plan to do this myself, partly
> because we are working on a Sage-LMFDB interface which would allow this
> additional data (and more) to be downloaded directly from the LMFDB,
> making this spkg redundant except for those need offline access to the
> database.

The motivation for the packaging is sagemath ; if it gets to use more of
ecdata, then it will still be time to complete my source package.

Cheers,

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ae1b55d5-c34c-5857-6001-8d523afec29d%40laposte.net.

Re: [sage-devel] Cremona's database of elliptic curves over rationals : compilation?

['Julien Puydt' via sage-devel]

Hi,

Le 20/08/2019 à 17:02, John Cremona a écrit :
> Julien,
> 
> [By the way, the optional spkg which is relevant here is
> database_cremona_ellcurve and *not* elliptic_curves.]

Yes ; in Debian:
- sagemath's standard elliptic_curves is
sagemath-database-elliptic-curves (I'm the maintainer) ;
- sagemath's optional database_cremona_ellcurve will be
sagemath-database-cremona-elliptic-curves (I'll be the maintainer).

> I have tried your new py code to produce a new version of the database
> file: it appears to work perfectly, and will compare it with what the
> existing Sage code creates.  I know rather little about SQLITE -- should
> the resulting files be identical?  Even if not, I will try using both
> output db files and running all Sage tests.  The db files have the same
> size (613924864 bytes -- the new version will contain over 50 more
> curves than the old) so perhaps the only difference is the order in
> which data was added.  I'll test.

Thanks!

> I did also  need to patch sage/databases/cremona.py  since the build()
> function requires SAGE_SHARE to be imported.  Running that, I see that
> (as you may have noticed) there are many files in the ecdata repository
> / tarball which Sage does not use at all.  I adjusted the tar command to
> only extract the ones used.  (It would be possible for Sage to extract
> more and use more, but that is an issue for another day).

Yes, I was pondering just not shipping them.

> So I will soon post a new spkg at trac #28372.  Other than that, what is
> the plan?  I would like to add JP's python script to the ecdata/scripts
> directory for future use anyway.  I have wondered exactly why Sage's
> codebase contained this code for creating a specific new optional spkg. 
> Of course in the same file (src/databases/cremona) is code for creating
> the mini version of the database, but that is something which never
> needs to be updated.

I'm all for using a simple standalone Python script instead of depending
on all of sagemath...

Cheers,

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/da72a46e-62db-037b-e9fc-3c781a825a1e%40laposte.net.

Re: [sage-devel] Cremona's database of elliptic curves over rationals : compilation?

['Julien Puydt' via sage-devel]

Le 21/07/2019 à 13:19, John Cremona a écrit :
>  
> On Sat, 20 Jul 2019 at 21:08, 'Julien Puydt' via sage-devel
> mailto:sage-devel@googlegroups.com>> wrote:
> 
> Le 19/07/2019 à 16:41, John Cremona a écrit :
> 
> > Not written by me, just used by me to update Sage's optional package. 
> > William would remember who wrote it.
> 
> I crossed the build/pkgs/elliptic_curves and
> src/sage/databases/cremona.py files and obtained the following build
> script.
> 
> 
> I'm a bit annoyed because the elliptic_curve pkg ships a 470M
> cremona.db, and I get a 479M cremona.db ; but perhaps it's because I
> pack everything (no bound on the genus : everything in the files!)?
> 
> "genus" --> "conductor".  This would be explained (I think) by the fact
> that the shipped spkg goes up to conductor 400k while ecdata on github
> now goes up to 410k.  That's all.  I will soon have finished to 500k and
> then the spkg will presumably be around 500M.

Yes, conductor.

Could you add a nice LICENSE file to clarify things? I think it's public
domain since it's a list of mathematical objects... but I'd rather have
a nice file by the author to tell that :-P

Thanks,

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/63694530-e253-7c92-f0f5-2d2838d2e666%40laposte.net.

Re: [sage-devel] Cremona's database of elliptic curves over rationals : compilation?

['Julien Puydt' via sage-devel]

Le 19/07/2019 à 16:41, John Cremona a écrit :

> Not written by me, just used by me to update Sage's optional package. 
> William would remember who wrote it.

I crossed the build/pkgs/elliptic_curves and
src/sage/databases/cremona.py files and obtained the following build script.


I'm a bit annoyed because the elliptic_curve pkg ships a 470M
cremona.db, and I get a 479M cremona.db ; but perhaps it's because I
pack everything (no bound on the genus : everything in the files!)?

Does it look good?

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6a8ed2dc-7166-fe90-5f1e-f0956fab9386%40laposte.net.
#!/usr/bin/python3

import os
from sqlite3 import connect

def create_db():

target = 'cremona.db'

print("Creating database {0}".format(target))
if os.path.exists(target):
os.remove(target)

con = connect(target)

con.execute('CREATE TABLE t_class(conductor INTEGER,'
' class TEXT PRIMARY KEY, rank INTEGER, L REAL, deg INTEGER)')
con.execute('CREATE TABLE t_curve(class TEXT,'
' curve TEXT PRIMARY KEY, eqn TEXT UNIQUE,'
' gens TEXT, tors INTEGER, cp INTEGER,'
' om REAL, reg REAL, sha)')
con.execute('CREATE INDEX i_t_class_conductor ON t_class(conductor)')
con.execute('CREATE INDEX i_t_curve_class ON t_curve(class)')

return con

def populate_allcurves(con):
print('Inserting all curves')
for filename in sorted(os.listdir('allcurves')):
class_data = []
curve_data = []
with open(os.path.join('allcurves', filename)) as fich:
print('\tConsidering {0}'.format(filename))
for line in fich.readlines():
N, iso, num, ainvs, r, tor = line.split()
cls = N+iso
cur = cls+num
if num == "1":
class_data.append((N,cls,r))
curve_data.append((cur,cls,ainvs,tor))
con.executemany('INSERT INTO t_class (conductor,class,rank)'
' VALUES (?,?,?)', class_data)
con.executemany('INSERT INTO t_curve (curve,class,eqn,tors)'
' VALUES (?,?,?,?)', curve_data)
con.commit()

def populate_allbsd(con):
print('Inserting all BSD')
for filename in sorted(os.listdir('allbsd')):
# why, oh why? There's a single problematic file...
if not filename.startswith('allbsd'):
break
class_data = []
curve_data = []
with open(os.path.join('allbsd', filename)) as fich:
print('\tConsidering {0}'.format(filename))
for line in fich.readlines():
N, iso, num, eqn, rank, tor, cp, om, L, reg, sha  = line.split()
cls = N+iso
if num == "1":
class_data.append((L,cls))
curve_data.append((cp,om,reg,eval(sha),cls+num))
con.executemany("UPDATE t_class SET L=? WHERE class=?", class_data)
con.executemany("UPDATE t_curve SET cp=?,om=?,reg=?,sha=? WHERE "
" curve=?", curve_data)
con.commit()

def populate_allgens(con):
print('Inserting all gens')
for filename in sorted(os.listdir('allgens')):
curve_data = []
with open(os.path.join('allgens', filename)) as fich:
print('\tConsidering {0}'.format(filename))
for line in fich.readlines():
v = line.split()
gens = '['+','.join(v[6:6+int(v[4])]).replace(':',',')+']'
curve_data.append((gens,''.join(v[:3])))
con.executemany("UPDATE t_curve SET gens=? WHERE curve=?",
curve_data)
con.commit()

def populate_degphi(con):
print('Inserting all degphi')
for filename in sorted(os.listdir('degphi')):
class_data = []
with open(os.path.join('degphi', filename)) as fich:
print('\tConsidering {0}'.format(filename))
for line in fich.readlines():
N, iso, num, degree, primes, curve = line.split()
class_data.append((degree,N+iso))
con.executemany('UPDATE t_class SET deg=? WHERE class=?',
class_data)
con.commit()

def repack(db):
print('Repacking the database')
con.execute('VACUUM')

if __name__ == '__main__':
con = create_db()
populate_allcurves(con)
populate_allbsd(con)
populate_allgens(con)
populate_degphi(con)
repack(con)
con.close()

Re: [sage-devel] Cremona's database of elliptic curves over rationals : compilation?

['Julien Puydt' via sage-devel]

Le 19/07/2019 à 15:53, John Cremona a écrit :
> The code to create the database is in Sage itself. 
> See 
> https://github.com/sagemath/sage/blob/master/src/sage/databases/cremona.py.

Oh, dear... I'll see if I can't turn it into a much shorter piece of code...

> I recommend that you hold off for a short while since I am about to
> update the database to include all conductors up to 50 (now it is
> 40).  This is thanks to Andrew Sutherland + Simon Foundation +
> Google CP, which ran 80,000 simultaneous jobs on 600,000 cores last
> night.  So right now I am drowning in data but it will all be sorted
> before long.

Oh! That sounds like an amazing project!

I can still try to prepare the package with the old data, and only
upload to Debian when the new data is there.

Thanks!

JP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/65226129-a3dc-5805-3760-23b1b3a5388b%40laposte.net.

[sage-devel] Cremona's database of elliptic curves over rationals : compilation?

['Julien Puydt' via sage-devel]

Hi,

I'm considering packaging this database for Debian.

I have upstream files: https://github.com/JohnCremona/ecdata

I know sagemath wants a cremona.db sqlite3 database, as that's what is
in the src/ for the pkg.

What I miss is the file turning the data files into the database!

For the smaller database, there is:
https://git.sagemath.org/sage.git/tree/build/pkgs/elliptic_curves/spkg-install.py

But as far as I can tell the two databases don't even have the same format:
https://git.sagemath.org/sage.git/tree/src/sage/databases/cremona.py

Can someone lend a hand?

JP

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/922ea2c1-1525-7060-4bbb-06a268f64f5b%40laposte.net.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Import issue for Sage when using the system's Python (e.g. Debian)

['Julien Puydt' via sage-devel]

Le 10/01/2019 à 22:03, Jeroen Demeyer a écrit :

On 2019-01-10 21:51, 'Julien Puydt' via sage-devel wrote:

Didn't François mention changing SAGE_ROOT wasn't needed?


He said

SAGE_ROOT should only be needed for the packaging system
and possibly the doctests. I regard any needs for SAGE_ROOT at runtime
a bug.


In other words: it is still needed, but that's a bug. And I agree with 
that.



https://trac.sagemath.org/ticket/27040


JP

--
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] Import issue for Sage when using the system's Python (e.g. Debian)

['Julien Puydt' via sage-devel]

Hi,

Le 10/01/2019 à 21:48, Jeroen Demeyer a écrit :

On 2019-01-10 20:46, 'Julien Puydt' via sage-devel wrote:

Perhaps upstream would accept such a trivial change?


If you make a ticket for it, sure. But it won't help with SAGE_ROOT.


Didn't François mention changing SAGE_ROOT wasn't needed?

JP

--
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] Import issue for Sage when using the system's Python (e.g. Debian)

['Julien Puydt' via sage-devel]

Le 10/01/2019 à 20:07, François Bissey a écrit :

I have recently made the following change in sage-on-gentoo’s env.py
_add_variable_or_fallback('SAGE_LOCAL',  sysconfig.get_config_var("prefix”))

which means SAGE_LOCAL is now pulled from the system rather than
a seeded value (as it was before).



Perhaps upstream would accept such a trivial change?

JP

--
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] python3 report (end of august 2018)

['Julien Puydt' via sage-devel]

Hi,

On 26/08/2018 17:47, Frédéric Chapoton wrote:
The patchbot report on sage+python3  for 8.4.b2 has still *many* (and I 
mean *_many_*) failing doctests. But it also stops badly in the way 
shown below, complaining that too many files are open. Could somebody 
investigate this issue, please ?
That probably means the doctesting framework is leaking file 
descriptors, ie: it opens each and every file but never closes them.


I would search:
(1) either a single piece of code which does all the opening and never 
closes anything during the whole run (the least likely scenario)
(2) or a piece of code forking correct workers (ie: they would 
open+close correctly) but leaking them (so the closing part doesn't 
happen) (the most likely scenario).


Someone familiar with the code should probably have a look and would be 
more efficient at spotting the problem.


jpuydt on irc.debian.org

--
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] GNU/Linux debian sid/testing: "Error building Sage" 8.3 from git

['Julien Puydt' via sage-devel]

Hi,

Le 17/08/2018 à 11:17, Jörg-Volker a écrit :

Another question I have after looking at the binary package of sage for 
debian 9 is: how was that built? Since in this package all packages 
using blas and lapack are linked against the system libraries 
libblas.so, liblapack.so, and libopenblas.so.


Building sage isn't as simple as we'd like yet:
https://wiki.debian.org/DebianScience/Sage

jpuydt on irc.debian.org

--
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] GNU/Linux debian sid/testing: "Error building Sage" 8.3 from git

['Julien Puydt' via sage-devel]

Hi,

Le 14/08/2018 à 11:20, Jörg-Volker a écrit :


Hi,
trying to build Sage 8.3 on my GNU/Linux debian testing/sid system with 
local gcc suite version 8.2.0 fails while compiling scipy. This is on a 
desktop computer with 4 cores (8 threads) and 32 GB RAM.


I have no clue what "testing/sid" might be... since as far as I know 
"sid==unstable"



The build command was

MAKE='make -j8' SAGE_INSTALL_GCC=no SAGE_BUILD_DIR=/tmp/sage-b  make
build


The relevant log file shows

 Traceback (most recent call last):
   File "", line 1, in 
   File "/tmp/.cache-walt/pip-9Uwgks-build/setup.py", line 416, in 

 setup_package()
   File "/tmp/.cache-walt/pip-9Uwgks-build/setup.py", line 396, in 
setup_package
 from numpy.distutils.core import setup
   File
"/tmp/sage/sage.git-8.3/local/lib/python2.7/site-packages/numpy/__init__.py", 
line 142, in 
 from . import add_newdocs
   File
"/tmp/sage/sage.git-8.3/local/lib/python2.7/site-packages/numpy/add_newdocs.py", 
line 13, in 
 from numpy.lib import add_newdoc
   File
"/tmp/sage/sage.git-8.3/local/lib/python2.7/site-packages/numpy/lib/__init__.py", 
line 8, in 
 from .type_check import *
   File

"/tmp/sage/sage.git-8.3/local/lib/python2.7/site-packages/numpy/lib/type_check.py", 
line 11, in 
 import numpy.core.numeric as _nx
   File

"/tmp/sage/sage.git-8.3/local/lib/python2.7/site-packages/numpy/core/__init__.py", 
line 26, in 
 raise ImportError(msg)
 ImportError:
 Importing the multiarray numpy extension module failed.  Most
 likely you are trying to import a failed build of numpy.
 If you're working with a numpy git repo, try `git clean -xdf` (removes 
all
 files not under version control).  Otherwise reinstall numpy.

 Original error was: /usr/lib/x86_64-linux-gnu/libblas.so.3: undefined 
symbol: sgemv_thread_n

 Running setup.py install for scipy: finished with status 'error'

The system has OpenBLAS installed but with a newer version 0.3.2.

Any ideas?

I've built previous versions of Sage on this system before (with gcc 7.3.0).



Notice that there is a sagemath 8.3 in preparation for Debian, see :
https://people.debian.org/~thansen/debian-sage-status.html

so perhaps you could lend a hand making it to unstable?

jpuydt on irc.debian.org

--
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: VOTE: inclusion of OpenSSL in Sage

['Julien Puydt' via sage-devel]

Hi,

Le 25/10/2017 à 00:08, Eric Gourgoulhon a écrit :
> Le mardi 24 octobre 2017 20:58:17 UTC+2, Emmanuel Charpentier a écrit :
> 
> 
> It is true. But we are hoisted by our own petard : from our tutorial
>  :
> "The Sage download file comes with “batteries included”. In other
> words, although Sage uses Python, IPython, PARI, GAP, Singular,
> Maxima, NTL, GMP, and so on, you do not need to install them
> separately as they are included with the Sage distribution."
> I fail to see how this would not apply to OpenSSL (under the heading
> "and so on")...
> 
>  
> I have the feeling that the current tendency is towards a more modular
> and lighter Sage, which deviates from the original "batteries included"
> philosophy. Maybe the latter should be rephrased as "mathematical
> batteries included". This would exclude standard "technical"  software
> like OpenSSL, which should be provided systemwide.

I'd vote for a strict separation of sage-the-distribution and
sage-the-software : I'm not interested at all in the former, and I think
it hampers the latter for which I care.

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

Re: [sage-devel] Re: VOTE: inclusion of OpenSSL in Sage

['Julien Puydt' via sage-devel]

Le 23/10/2017 à 15:40, Emmanuel Charpentier a écrit :
> BTW : the vote closes in about 20 minutes. This is your last chance to
> take back any "too hasty" votes.

My vote: no openSSL now - wait until the license issues are solved

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

Re: [sage-devel] Use system R with sage?

['Julien Puydt' via sage-devel]

Hi,

Le 22/10/2017 à 10:17, Dima Pasechnik a écrit :
> my limited experience with helping advanced R users was that it is not really 
> possible for them to use R from Sage, as they needed R packages that in turn 
> needed Java runtime.
> 
> And they much preferred things done in R-studio.

At some point, the question of correctly separating
sage-the-distribution and sage-the-software will have to be tackled...

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

Re: [sage-devel] python3 status

['Julien Puydt' via sage-devel]

Hi,

Le 13/10/2017 à 17:56, Frédéric Chapoton a écrit :
> Cool, no ? Or maybe nobody cares ?

Extremely cool!

> Many things are still not working. The cmp problem has been much
> reduced, but still not fully fixed. On our way is a large-scale unicode
> problem, and maybe another large scale hash problem.

Why are unicode and hash problems?

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

Re: [sage-devel] Re: Faster way to load python code

['Julien Puydt' via sage-devel]

Hi,

Le 17/09/2017 à 11:56, Simon King a écrit :
> On 2017-09-17, Dima Pasechnik  wrote:
>> Isn't it what pickle/cPickle is for? 
> 
> I don't want to store data, I want to read them. And I am not the
> one who stored them. So, I have to take the textfiles as I get
> them.

You could have the textfiles *and* the pickles, with the following api:
- "refresh" loads the textfiles and dumps them to pickles (that is slow,
and done only when the textfiles are updated) ;
- "load" load the pickles (that is fast and is done most often).

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

Re: [sage-devel] Calculation Error

['Julien Puydt' via sage-devel]

Hi,

Le 26/08/2017 à 22:57, Dr. David Kirkby (Kirkby Microwave Ltd) a écrit :
> I'm not a mathematician, but believe 0^0 is undefined.

You can either consider 0^0 to be undefined or that it is 1 by
convention : both are "correct", and neither should be considered a bug.

Snark on #debian-science

-- 
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] python3 (not yet, and not for soon)

['Julien Puydt' via sage-devel]

Hi,

Le 07/08/2017 à 11:54, Erik Bray a écrit :

> I'm working on a better solution to this as part of a more general
> reworking of how Sage's dist handles dependencies that can be
> fulfilled by multiple packages (in this case the dependency being
> 'python'--specifically the Python used for Sage itself).  I have a
> prototype at [1] but there are several things about it I'm unhappy
> with, and I want to redo it on top of some even lower-level overhauls
> I'm working on (e.g. [2]).

I would like to make the point that having a packaging which is :
- versioned ;
- with dependency resolution ;
- including virtual packages ;
is definitely a sage-as-a-distribution problem.

Please take into account that sage-as-a-software should be kept easily
package-able by other distributions.

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

Re: [sage-devel] Re: Python3?

['Julien Puydt' via sage-devel]

Hi,

On 19/01/2017 18:44, William Stein wrote:

On Thu, Jan 19, 2017 at 9:39 AM, Jeroen Demeyer  wrote:

On 2017-01-19 17:17, William Stein wrote:


... and presumably what we already decided is now completely
impossible to implement and banned from Python3?



I don't think we ever decided anything. For Parents, we use Robert
Bradshaw's implementation from 2008 but it's not documented what it does or
why it does things that way. For example, there is a doctest

sage: ZZ < QQ
True

but I doubt that this is the right thing to do.


Let me rewrite the above: ... and presumably what we already
**implemented** is now completely
impossible to implement and banned from Python3?


Well, if it is implemented but doesn't really make sense, is it that big 
a problem to drop it for the transition to Python 3 ?


Snark on #debian-science

--
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: Python3?

['Julien Puydt' via sage-devel]

Hi,

On 19/01/2017 08:47, Frédéric Chapoton wrote:


The problem with cmp is quite hard, and it seems that every instance of
cmp() must be handled separately. I have gained some experience on the
subject, but given the lack of reviewers, this implies a very slow pace.
This cmp problem should be the last remaining thing to handle before
reaching 1A) and maybe even 1B)


is there some place with a good summary of the cmp situation, and can 
you point at some patches showing how the matter is fixed?


Thanks,

Snark on #debian-science

--
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] Release note auto-generation RFC

['Julien Puydt' via sage-devel]

On 12/01/2017 09:54, Kwankyu Lee wrote:

Wouldn't some directive like "If you think ticket #314159 is of wider
interest, all you have to do is to fill in the Changes-7.6.rst file"
make it possible to both drop this new tool and allow a richer
structure? Said Changes-.rst could start as a copy from a
Changes-template.rst with a prepared structured, which the release
manager would prune at the last moment to remove empty sections.

I guess the idea is to have one "news fragment" file for one merged
ticket instead of a single file that contains all news.


And my point is that this tool doesn't bring anything substantial : if 
you have to get out of your way to add something to the news, then at 
least do so for something nice and complete. In my opinion the 
categories provided by towncrier make it a tiny convenience for a small 
project and uninteresting for a large project.


Now, if towncrier made it possible to name the fragment files something 
like 314159.features.algebraic-geometry.elliptic-curves and generated a 
more structured changelog from that, that would be more convincing. 
[Using a dictionary somewhere to turn the various filename chunks into 
something human-readable and falling back to changing '-' to space and 
capitalizing the first word, say].


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

Re: [sage-devel] Release note auto-generation RFC

['Julien Puydt' via sage-devel]

Hi,

On 12/01/2017 00:09, Volker Braun wrote:

There is a somewhat painless approach to generating human-readable
release notes using https://github.com/hawkowl/towncrier. As far as the
ticket author is concerned, if you think that your ticket #12435 is of
wider interest and should be announced then all you'd have to do is add
a file

echo "Added the last twin prime" > newsfragments/12435.feature

Note that the fragment filename starts with the ticket number, so it
won't conflict with other news fragments. Then, when making a new
release, I concatenate the fragments into NEWS.rst as, for example,
in https://github.com/hawkowl/towncrier/blob/master/NEWS.rst


I have to point out that this isn't auto-generated since a specific 
command has to be entered.


I also notice that towncrier has pretty rough single-level structuring 
(feature, bugfix, doc, removal, misc), which might be a bit limitative 
for a large project like sagemath.


Wouldn't some directive like "If you think ticket #314159 is of wider 
interest, all you have to do is to fill in the Changes-7.6.rst file" 
make it possible to both drop this new tool and allow a richer 
structure? Said Changes-.rst could start as a copy from a 
Changes-template.rst with a prepared structured, which the release 
manager would prune at the last moment to remove empty sections.


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

Re: [sage-devel] Re: R 3.3.1 depends on a SSL/TLS implementation

['Julien Puydt' via sage-devel]

Hi,

On 28/10/2016 15:39, Emmanuel Charpentier wrote:


However, this does not seem to be a problem per se : Debian (one of the
most nitpicking distros in terms of licensing)   happily ships libraries
and utilities (such as cups, for starter) linked with openssl-linked
libcurl. I think that it would be interesting to ask them how they
reconcile the (inconsistent) wordings of the licenses involved.


It's easy to ask:

https://www.debian.org/legal/

Snark on #debian-science

--
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] Upstream links for purely sage package

['Julien Puydt' via sage-devel]

Hi,

On 07/10/2016 12:19, Jeroen Demeyer wrote:

On 2016-10-06 12:58, 'Julien Puydt' via sage-devel wrote:

For those sage-is-upstream packages, I was pointing the helper to
 http://files.sagemath.org/spkg/upstream/
but now it looks like those are not available anymore on the
sagemath.org server.


I believe that this is a temporary outage of the files.sagemath.org server.



I asked because it lasted since a few days, but indeed it looks like 
everything is back.


Thanks!

Snark on #debian-science

--
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] Upstream links for purely sage package

['Julien Puydt' via sage-devel]

Hi,

I'm the maintainer of a few Debian packages, for which sage is 
considered upstream:

   rubiks
   sagemath-database-mutually-combinatorial-designs
   sagemath-database-conway-polynomials
   sagemath-database-elliptic-curves
   sagemath-database-graphs
   sagemath-database-polytopes

To detect when a new upstream is available, Debian uses a helper, which 
analyses homepages/download pages to see which versions are available 
(uscan).


For those sage-is-upstream packages, I was pointing the helper to
http://files.sagemath.org/spkg/upstream/
but now it looks like those are not available anymore on the 
sagemath.org server.


I could point to mirrors, like say:
http://www-ftp.lip6.fr/pub/math/sagemath/spkg/upstream/
but I think it would be better to have a real upstream link.

Let me insist : the links are used to check for new versions, by either 
developers working on the package, or by the Debian servers to update 
status page ; downloading the sources of a new version is done by hand 
(well, triggered by hand -- using the helper script in download mode), 
by developers : users of the Debian packages then get the sources from 
Debian mirrors. It shouldn't overload the main servers.


Can you point me to a correct place?

Thanks,

Snark on #debian-science

--
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: What in Sage uses Boost ? And who maintains it ?

['Julien Puydt' via sage-devel]

Polybori is now brial if I remember well.

Snark on? #sagemathLe 11 nov. 2015 15:21, Simon King  
a écrit :
>
> Hi! 
>
> On 2015-11-11, 'Martin Albrecht' via sage-devel  
> wrote: 
> >> 1) What in Sage uses Boost ? 
> > 
> > I know this one: PolyBoRi. 
> >  
> >> 2) Is someone maintaining it ? 
>
> Wasn't there some discussion to remove PolyBoRi? 
>
> Cheers, 
> 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 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] which computation is right?

['Julien Puydt' via sage-devel]

Hi,

Le 20/10/2015 22:28, Sarfo a écrit :

could anyone please tell me which computation evaluated in the attached
file is right?
Thank you.


All of them?

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.

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.

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

['Julien Puydt' via sage-devel]

Le lundi 12 oct. 2015 à 13:50:04 (+0100), Alexander Konovalov a écrit :
> we are happy to announce the First Joint GAP-​Sage Days which 
> will take place in St Andrews on January 18th-22nd, 2016. They 
> will be preceded by a GAP Coding Sprint on January 13th-16th.
> 
> For the 1st Joint GAP-Sage Days, the focus of the workshop will 
> be on improving GAP-SageMath integration and interaction between 
> our systems and between their developers. The focus of the GAP 
> Coding Sprint will be on converging GAP and HPC-GAP development 
> branches.

Does that mean that the libgap in sagemath will get part of upstream GAP?

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.

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

['Julien Puydt' via sage-devel]

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.

Cheers,

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.

Re: [sage-devel] Fwd: Re: nauty in Sage

['Julien Puydt' via sage-devel]

Hi,

Le vendredi 09 oct. 2015 ą 07:30:06 (-0700), Dima Pasechnik a écrit :
> On Thursday, 8 October 2015 11:46:34 UTC-7, Jeroen Demeyer wrote:
> >
> > On 2015-10-08 20:22, Dima Pasechnik wrote: 
> > > if it talks about changes, this means changes are allowed, no? 
> > Well, in principle I agree, but it's safer not to assume anything. 
> >
> 
> Brendan replied that remaining two clauses in the license fall under Sect. 
> 7 of  GPL v3.
> 
> Indeed the latter does allow extra clauses to be added, no?
> 

Hmmm... will he publish a full version with this copyright notice? Because
if he does, then distributions could start packaging it.

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.

Re: [sage-devel] Fwd: Re: nauty in Sage

['Julien Puydt' via sage-devel]

Le vendredi 09 oct. 2015 à 09:43:31 (-0700), Dima Pasechnik a écrit :
>
> On Friday, 9 October 2015 09:26:48 UTC-7, Nathann Cohen wrote:
> >
> > > we talk about nauty being included into Sage - the permission is being 
> > given 
> > > for this, and only this, AFAIU... 
> >
> > I don't think that " + must only be used in Sage" is 
> > GPL-compatible. 
> >
> 
> As long we we do not write this in... 
> I suppose I should make it clear for Brendan that someone will be able to 
> create a Sage fork consisting of nauty 
> under essentially GPL.

William had a point when he said : stick to a known license, don't try
to invent your own.

The author might actually be interested by BSD-3-clause, in fact.

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.