[sage-devel] Fwd: SageMath packaging status update

[Jan Groenewald]

Might of interest to some here.  Please join the mailing list if you can
help.

-- Forwarded message --
From: Tobias Hansen 
Date: 10 August 2016 at 01:17
Subject: SageMath packaging status update
To: "debian-scie...@lists.debian.org" 


Hi Debian Science,

I thought I'd give you an update about the packaging of SageMath in Debian.

Since the last update we have improved our methods quite a bit. We now
have a mini-dinstall (our own little APT repository) which allows us to
always have a set of packages available that makes it possible to build
SageMath. We have an up-to-date SageMath (7.3) that can be built using
Debian packages to fulfill most dependencies. One can run the test
suite, but we didn't create an installable package yet.

We are currently working on packaging the last small dependencies and
making the tests pass. Help is always welcome, it would be awesome if we
could manage to ship SageMath in Stretch. More details can be found on
the Wiki page [1].

Since today we also have our own mailing list to discuss issues
regarding SageMath packaging. [2]

Best,
Tobias

[1] https://wiki.debian.org/DebianScience/Sage
[2] https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath




-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
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] fast_callable interpreter for MPC?

[Nils Bruin]

A quick inquiry:

I noticed that fast_callable(...,domain=RealField(...) ) results in 
instances of RRInterpreter, which is nice and fast. On the other hand, 
fast_callable(...,domain=ComplexField(...)) results in a more generic type 
(and something that is considerably slower, at least for polynomials).

Does someone have code lying around to make an interpreter that wraps MPC? 
Is there interest in producing such an interpreter? It looks like it should 
be a relatively straightforward job of copying and adjusting the 
RRInterpreter and StorageTypeMPFR classes ... I might be able to do it 
myself, but for someone with experience doing this it might be a much 
easier task. I have an interesting application for computing Riemann 
matrices to high precision (the only code I am aware of that can do this 
presently is in Maple).

-- 
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: Should warnings display a traceback?

[Travis Scrimshaw]

On Tuesday, August 9, 2016 at 2:31:16 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2016-08-09 00:21, Travis Scrimshaw wrote: 
> > If we do this, then deprecation warnings would also get full tracebacks, 
> > which is something I think we should not have on by default. 
>
> Why not? It's not that you need to put the complete traceback in the 
> doctest, you can use ... for that. So you would only see the traceback 
> if a doctest fails, and then the traceback can actually be useful. 
>

It would be useful when you have something deep in the code (which is 
probably not something deep in Sage's source code, but in your personal 
code) that you need to remove. However, it could be seen as annoying, or 
worse, scary because it would look so much like an error traceback, to a 
typical user who just wants to run some simple code. Yes, they should 
change, but it can be hard to break simple habits.

>
> > However, it 
> > might be good to have an option somewhere to enable is (and hopefully it 
> > won't get lost in the forest that is Sage). 
>
> Well, it seems we both agree that there are too many options already. 
>
 
Actually, it is more of it getting lost in everything, not that there are 
too many options. Something simple like changing the deprecation message to 
indicate that this option is there would alleviate this.

Best,
Travis

-- 
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] patchbot server refuses to connect

[William Stein]

OK, leaving it as -- not rebooting.

On Tue, Aug 9, 2016 at 12:51 AM, Frédéric Chapoton 
wrote:

> Please do not reboot. We are currently doing an rsync for the database,
> and we decided to turn the server off  for a moment.
>
> Thierry Monteil is doing the job. Maybe he can tell us about the status ?
>
> Le mardi 9 août 2016 08:18:25 UTC+2, William a écrit :
>>
>> On Mon, Aug 8, 2016 at 10:11 PM, Ralf Stephan  wrote:
>> > It is pingable however.
>>
>> I can try to reboot the computer again, maybe.  As before, I'm not
>> even sure which computer it's hosted on, and frankly I don't even want
>> to touch it unless somebody will very clearly volunteer to immediately
>> migrate it to Google Compute Engine the moment I get it restarted.  I
>> really can't believe nobody did so already...
>>
>>  - William
>>
>> --
>> William (http://wstein.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.
>



-- 
William (http://wstein.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.

[sage-devel] Re: Issues when building Sage with --with-mp=gmp

[leif]

leif wrote:
> Francois Bissey wrote:
>>
>>> On 31/07/2016, at 18:54, leif  wrote:
>>>
>>> This is what I get with GMP 6.1.1 (Sage 7.3.rc0, GCC 5.4.0):
>>>
>>> --
>>> sage -t --long --warn-long 68.2 src/sage/structure/sage_object.pyx  #
>>> Killed due to abort
>>> sage -t --long --warn-long 68.2 src/sage/rings/integer.pyx  # 1 doctest
>>> failed
>>> sage -t --long --warn-long 68.2 src/sage/homology/simplicial_complex.py
>>> # 1 doctest failed
>>> sage -t --long --warn-long 68.2 src/doc/en/developer/coding_in_other.rst
>>> # 1 doctest failed
>>> sage -t --long --warn-long 68.2
>>> src/doc/en/constructions/algebraic_geometry.rst  # 1 doctest failed
>>> sage -t --long --warn-long 68.2 src/sage/matrix/matrix_double_dense.pyx
>>> # 1 doctest failed
>>> sage -t --long --warn-long 68.2 src/sage/libs/libecm.pyx  # 1 doctest failed
>>> sage -t --long --warn-long 68.2 src/sage/ext/memory.pyx  # 1 doctest failed
>>> --
>>
>> I’ll assume this is a build from scratch with gmp.
>> I think coding_in_other.rst and algebraic_geometry.rst
>> are basically the same kind of errors. I had them for a while
>> and then they disappeared. The failure is triggered because
>> the order of the terms in the output is different.
> 
> Yes...  But not caused by GMP, but by Singular not using FLINT when
> (only) libgmp (not in addition libmpir) is installed (cf. #21188).
> 
> 
>> [...]
>>
>> The rest is new to me. Would have to dig difference between
>> your ntl/singular and mine at least.
> 
> The crash in sage_object.pyx (in unpickle_all(), NTL aborting because a
> modular inverse doesn't exist) also vanishes when Singular / libsingular
> again uses FLINT, cf. #5838.

P.S.:  Just checked:

These three doctests fail in exactly the same way when building Sage
with MPIR and configuring Singular --without-flint.


-leif


-- 
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] increasing verbose level for sub-routines

[William Stein]

On Tuesday, August 9, 2016, Volker Braun  wrote:

> The only good way is to rip out the "verbose" thing and replace it with
> the Python logging module. Then its easy to have different loggers for your
> code and for the flint interface, and make them log in different levels
> and/or different output streams.
>
>
You don't have rip out verbose and replace it.  Just switch to using
the built in Python logging module for what you're doing.   We should also
reimplement verbose on top of pythons built in logging module (probably
just a few lines of code to do that).  I'm very surprised nobody has done
this already.


>
>
>
> On Tuesday, August 9, 2016 at 11:42:32 AM UTC+2, Daniel Krenn wrote:
>>
>> Say I have some function doing something:
>>
>> sage: def f(M):
>> : A = M  # something will be done here
>> : verbose('something', 1)
>> : iA = A^(-1)
>> : return iA
>>
>> Setting the level of verbosity to 1 gives the output
>>
>> sage: set_verbose(1)
>> sage: f(Matrix([[1, 2], [3, 4]]))
>> verbose 1 (f) something (time = -0.092)
>> verbose 1 (f) computing inverse of 2 x 2 matrix using FLINT
>> [  -21]
>> [ 3/2 -1/2]
>>
>> How to repress the second verbose ("inverse...FLINT")?
>>
>> Ideally there would be something that increases all verbosity levels of
>> the functions I call within f, so that the messages are still there when
>> calling f with level >= 2, but leaves level 1 for my high-level function.
>>
>> Any ideas how to accomplish this (in a good way)?
>>
>> Best
>>
>> Daniel
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com
> 
> .
> To post to this group, send email to sage-devel@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my massive iPhone 6 plus.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: increasing verbose level for sub-routines

[Volker Braun]

The only good way is to rip out the "verbose" thing and replace it with the 
Python logging module. Then its easy to have different loggers for your 
code and for the flint interface, and make them log in different levels 
and/or different output streams.




On Tuesday, August 9, 2016 at 11:42:32 AM UTC+2, Daniel Krenn wrote:
>
> Say I have some function doing something: 
>
> sage: def f(M): 
> : A = M  # something will be done here 
> : verbose('something', 1) 
> : iA = A^(-1) 
> : return iA 
>
> Setting the level of verbosity to 1 gives the output 
>
> sage: set_verbose(1) 
> sage: f(Matrix([[1, 2], [3, 4]])) 
> verbose 1 (f) something (time = -0.092) 
> verbose 1 (f) computing inverse of 2 x 2 matrix using FLINT 
> [  -21] 
> [ 3/2 -1/2] 
>
> How to repress the second verbose ("inverse...FLINT")? 
>
> Ideally there would be something that increases all verbosity levels of 
> the functions I call within f, so that the messages are still there when 
> calling f with level >= 2, but leaves level 1 for my high-level function. 
>
> Any ideas how to accomplish this (in a good way)? 
>
> Best 
>
> Daniel 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Issues when building Sage with --with-mp=gmp

[leif]

Francois Bissey wrote:
> 
>> On 31/07/2016, at 18:54, leif  wrote:
>>
>> This is what I get with GMP 6.1.1 (Sage 7.3.rc0, GCC 5.4.0):
>>
>> --
>> sage -t --long --warn-long 68.2 src/sage/structure/sage_object.pyx  #
>> Killed due to abort
>> sage -t --long --warn-long 68.2 src/sage/rings/integer.pyx  # 1 doctest
>> failed
>> sage -t --long --warn-long 68.2 src/sage/homology/simplicial_complex.py
>> # 1 doctest failed
>> sage -t --long --warn-long 68.2 src/doc/en/developer/coding_in_other.rst
>> # 1 doctest failed
>> sage -t --long --warn-long 68.2
>> src/doc/en/constructions/algebraic_geometry.rst  # 1 doctest failed
>> sage -t --long --warn-long 68.2 src/sage/matrix/matrix_double_dense.pyx
>> # 1 doctest failed
>> sage -t --long --warn-long 68.2 src/sage/libs/libecm.pyx  # 1 doctest failed
>> sage -t --long --warn-long 68.2 src/sage/ext/memory.pyx  # 1 doctest failed
>> --
> 
> I’ll assume this is a build from scratch with gmp.
> I think coding_in_other.rst and algebraic_geometry.rst
> are basically the same kind of errors. I had them for a while
> and then they disappeared. The failure is triggered because
> the order of the terms in the output is different.

Yes...  But not caused by GMP, but by Singular not using FLINT when
(only) libgmp (not in addition libmpir) is installed (cf. #21188).


> [...]
> 
> The rest is new to me. Would have to dig difference between
> your ntl/singular and mine at least.

The crash in sage_object.pyx (in unpickle_all(), NTL aborting because a
modular inverse doesn't exist) also vanishes when Singular / libsingular
again uses FLINT, cf. #5838.


-leif


-- 
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: Should warnings display a traceback?

[leif]

Jeroen Demeyer wrote:
> On 2016-08-09 00:21, Travis Scrimshaw wrote:
>> However, it
>> might be good to have an option somewhere to enable is (and hopefully it
>> won't get lost in the forest that is Sage).
> 
> Well, it seems we both agree that there are too many options already.

You cannot have too many options.

You can have poor default settings, poor documentation, and poor ways to
set them, probably also inconsistent implementations.


(I'm not saying that all of this applies to Sage.  And to each option,
any combination of the above may apply.)


-leif


-- 
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] d3js question.

[Thierry Dumont]

Hello,

It seems that Sage can make some usage of d3.js

->
http://sagemanifolds.obspm.fr/doc/reference/graphs/sage/graphs/graph_plot_js.html
-> their exists a d3js package (which seems to install the library /
javascript)

But d3.js seems to be used only to draw graphs. Am I wrong ?

>From an other side, their exists different interfaces ro d3.js in
Python: Python-nvd3, mpld3 ...

d3 is a very nice library (my opinion...).

mpld3 is easy to install in sage (sage -pip...).

Are there some projects about this ? some users ?

t.d.

-- 
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] fplll 5.0 in sage

[Jean-Pierre Flori]

Yes!

Did you open a ticket for this?

-- 
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] increasing verbose level for sub-routines

[Daniel Krenn]

Say I have some function doing something:

sage: def f(M):
: A = M  # something will be done here
: verbose('something', 1)
: iA = A^(-1)
: return iA

Setting the level of verbosity to 1 gives the output

sage: set_verbose(1)
sage: f(Matrix([[1, 2], [3, 4]]))
verbose 1 (f) something (time = -0.092)
verbose 1 (f) computing inverse of 2 x 2 matrix using FLINT
[  -21]
[ 3/2 -1/2]

How to repress the second verbose ("inverse...FLINT")?

Ideally there would be something that increases all verbosity levels of
the functions I call within f, so that the messages are still there when
calling f with level >= 2, but leaves level 1 for my high-level function.

Any ideas how to accomplish this (in a good way)?

Best

Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] patchbot server refuses to connect

[Frédéric Chapoton]

Please do not reboot. We are currently doing an rsync for the database, and 
we decided to turn the server off  for a moment.

Thierry Monteil is doing the job. Maybe he can tell us about the status ?

Le mardi 9 août 2016 08:18:25 UTC+2, William a écrit :
>
> On Mon, Aug 8, 2016 at 10:11 PM, Ralf Stephan  > wrote: 
> > It is pingable however. 
>
> I can try to reboot the computer again, maybe.  As before, I'm not 
> even sure which computer it's hosted on, and frankly I don't even want 
> to touch it unless somebody will very clearly volunteer to immediately 
> migrate it to Google Compute Engine the moment I get it restarted.  I 
> really can't believe nobody did so already... 
>
>  - William 
>
> -- 
> William (http://wstein.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: Should warnings display a traceback?

[Jeroen Demeyer]

On 2016-08-09 00:21, Travis Scrimshaw wrote:

If we do this, then deprecation warnings would also get full tracebacks,
which is something I think we should not have on by default.


Why not? It's not that you need to put the complete traceback in the 
doctest, you can use ... for that. So you would only see the traceback 
if a doctest fails, and then the traceback can actually be useful.



However, it
might be good to have an option somewhere to enable is (and hopefully it
won't get lost in the forest that is Sage).


Well, it seems we both agree that there are too many options already.

--
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] patchbot server refuses to connect

[Ralf Stephan]

Thanks. I always try to help with such things but mostly lose because I'm
lacking server admin skills.

On Tue, Aug 9, 2016 at 8:18 AM William Stein  wrote:

> On Mon, Aug 8, 2016 at 10:11 PM, Ralf Stephan  wrote:
> > It is pingable however.
>
> I can try to reboot the computer again, maybe.  As before, I'm not
> even sure which computer it's hosted on, and frankly I don't even want
> to touch it unless somebody will very clearly volunteer to immediately
> migrate it to Google Compute Engine the moment I get it restarted.  I
> really can't believe nobody did so already...
>
>  - William
>
> --
> William (http://wstein.org)
>
> --
> 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/vKcWSYpOb5I/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] patchbot server refuses to connect

[William Stein]

On Mon, Aug 8, 2016 at 10:11 PM, Ralf Stephan  wrote:
> It is pingable however.

I can try to reboot the computer again, maybe.  As before, I'm not
even sure which computer it's hosted on, and frankly I don't even want
to touch it unless somebody will very clearly volunteer to immediately
migrate it to Google Compute Engine the moment I get it restarted.  I
really can't believe nobody did so already...

 - William

-- 
William (http://wstein.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.