[sage-devel] Why packages tarballs have to be in lowercase ?

The Developer's guide states the ported packages' tarballs have to be in *lower case* : "The build scripts and associated files are in a subdirectory SAGE_ROOT/build/pkgs/package, where you replace package with a lower-c

[sage-devel] Re: Change of semantics for 'show'

Am Donnerstag, 30. April 2015 05:56:11 UTC+2 schrieb Volker Braun: > > On Wednesday, April 29, 2015 at 11:37:38 PM UTC-4, Martin R wrote: >> >> Oh, now that's an explanation! So the explanation in the third post on >> this thread, >> displayhook: calls __repr__ on the value of the last stat

[sage-devel] Re: Please review trac#18229.

After the closing of a Mac Xcode problem (trac#18254 ), trac#18229 , which now upgrades R to 3.2.0, needs review (again). HTH, -- Emmanuel Charpentier Le jeudi 16 avril 2015 22:49:52 UTC+2, Emmanuel Charpentier a éc

Re: [sage-devel] Re: Factoring p-adic polynomials

On 2015-04-29 17:49, Nils Bruin wrote: effectively we probably work with factorization of polynomials in (Z/p^nZ)[x], where f cannot be distinguished from polynomials that come from the square-free locus. Yes, that's true. -- You received this message because you are subscribed to the Google Gr

[sage-devel] Re: Poll: Which objects should be plotted by default in the notebook?

So far the objections have already been discussed on trac. I know, TL;DR: * You can turn it off: %display plot_graphs never * The console has it turned off by default, this is only a question for UIs that can display inline graphics. * Some graphs have displayed themselves graphically in the Sa

[sage-devel] Re: Change of semantics for 'show'

On Wednesday, April 29, 2015 at 11:37:38 PM UTC-4, Martin R wrote: > > Oh, now that's an explanation! So the explanation in the third post on > this thread, > displayhook: calls __repr__ on the value of the last statement and > sends to stdout > was a bit misleading. > Well that was about

[sage-devel] Re: Change of semantics for 'show'

Oh, now that's an explanation! So the explanation in the third post on this thread, displayhook: calls __repr__ on the value of the last statement and sends to stdout was a bit misleading. Thanks for clarifying. (In turn, this begs the question, when is repr used for display instead of

[sage-devel] Re: GP out of memory while testing Sage-6.6

Andrey Novoseltsev wrote: > I don't think I've seen it reported before: running "make ptestlong" on > Sage-6.6 after distclean crashed my server last night. Similar has been reported to sage-release about two weeks ago: http://thread.gmane.org/gmane.comp.mathematics.sage.release/2757 -leif --

Re: [sage-devel] Re: GP out of memory while testing Sage-6.6

OK, since this is not just me and it crushes machines: http://trac.sagemath.org/ticket/18340 On Wednesday, 29 April 2015 15:49:29 UTC-6, John Cremona wrote: > > I have seen similar things (also with lseries_ell and gp) and will not > do make testlong or ptestlong until it has been fixed since it

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Apr 29, 2015 7:30 AM, "Dima Pasechnik" wrote: >> > >> > this patch should go into Sage proper, as it also fixes the same as with SMC >> > issue with Sage's notebook. >> > >> >> Sure. What is the best way to make that happen? > > the usual way is via trac.sagemath.org > (for instance using git

Re: [sage-devel] Re: GP out of memory while testing Sage-6.6

I have seen similar things (also with lseries_ell and gp) and will not do make testlong or ptestlong until it has been fixed since it is not fair on other users of the machine. No problem with the build though. I know that I should help to diagnose and fix this since it is a functionality which I

[sage-devel] Re: Change of semantics for 'show'

I probably don't understand your question, so let me try a different answer in the hopes that that is what you were asking: The _rich_repr_() method is always called by the displayhook. If the object doesn't have one (AttributeError), or if it does not return anything (i.e. returns None) then w

[sage-devel] Re: GP out of memory while testing Sage-6.6

Same story with 6.7.beta3 -- 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@

[sage-devel] Re: Change of semantics for 'show'

I don't understand this answer. Am I the only one who doesn't get it? If so, don't bother to explain, I'm giving up. (I looked for _rich_repr on trac which gives me 9 tickets, none of which looked like it would explain to me when rich_repr is called, and I searched the online doc for rich_rep

[sage-devel] GP out of memory while testing Sage-6.6

Hello, I don't think I've seen it reported before: running "make ptestlong" on Sage-6.6 after distclean crashed my server last night (Debian Wheezy with 3.16 kernel, 2x Opteron 6272, 16 cores each, 128GB RAM, 64GB swap). Today the machine was unresponsive, on reboot logs have shown killing proc

[sage-devel] Re: Change of semantics for 'show'

On Wednesday, April 29, 2015 at 9:52:19 AM UTC-4, Martin R wrote: > > But why do we get _rich_repr_ on the console in the first place??? > * display ascii art as rich representation on the console * launch viewer when a Graphics object hits the displayhook -- You received this message because

Re: [sage-devel] Poll: Which objects should be plotted by default in the notebook?

On Apr 29, 2015, at 08:15 , Nathann Cohen wrote: > Hello everybody, > > In #18289 [2], Volker is improving the Notebook interface by making > some objects be automatically plotted by __repr__ [1] > >graphs.PetersenGraph() # this graph is plotted > > or > >P = posets.ChainPoset(10) # n

[sage-devel] Re: Poll: Which objects should be plotted by default in the notebook?

Hello ! There are lots of things that could have plots that should not have them > unless specifically requested. E.g. matrices, graphs, posets... This would > be a pretty big change to start bringing up plots in such cases. (Like > matrices - yikes!) > My opinion on this is simple: - I do

[sage-devel] Re: Poll: Which objects should be plotted by default in the notebook?

> > > > > In #18289 [2], Volker is improving the Notebook interface by making > > some objects be automatically plotted by __repr__ [1] > > > > graphs.PetersenGraph() # this graph is plotted > > > > or > > > > P = posets.ChainPoset(10) # no plot > > P # here, P is plotted > >

[sage-devel] Re: Poll: Which objects should be plotted by default in the notebook?

Nathann Cohen wrote: > Hello everybody, > > In #18289 [2], Volker is improving the Notebook interface by making > some objects be automatically plotted by __repr__ [1] > > graphs.PetersenGraph() # this graph is plotted > > or > > P = posets.ChainPoset(10) # no plot > P # here, P is

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

On Wednesday, April 29, 2015 at 1:11:22 AM UTC-7, jplab wrote: > > Hi, > > I had not noticed that Polyhedron created a Poset, and if so that 'makes >> sense'. I had the same problem with both classes: it makes it very hard to >> create a lot of Polyhedron objects, or many posets (and this, in tur

Re: [sage-devel] Re: Factoring p-adic polynomials

On Wednesday, April 29, 2015 at 3:15:44 AM UTC-7, Jeroen Demeyer wrote: > > No, it's not, the trailing coefficient is O(5^20): > > sage: R. = Qp(5)[] > sage: f = x^2 > sage: parent(f[0]) > 5-adic Field with capped relative precision 20 > Note the capped *relative* precision. These are "floats*

[sage-devel] Poll: Which objects should be plotted by default in the notebook?

Hello everybody, In #18289 [2], Volker is improving the Notebook interface by making some objects be automatically plotted by __repr__ [1] graphs.PetersenGraph() # this graph is plotted or P = posets.ChainPoset(10) # no plot P # here, P is plotted So far he only implemented it for

[sage-devel] Re: Change of semantics for 'show'

But why do we get _rich_repr_ on the console in the first place??? Martin Am Mittwoch, 29. April 2015 15:48:13 UTC+2 schrieb Volker Braun: > > On Wednesday, April 29, 2015 at 7:16:20 AM UTC-4, Martin R wrote: >> >> I have read this thread, but I fail to understand the reason. Eg., there >> is a

[sage-devel] Re: Change of semantics for 'show'

On Wednesday, April 29, 2015 at 7:16:20 AM UTC-4, Martin R wrote: > > I have read this thread, but I fail to understand the reason. Eg., there > is a commit "extrawurst for graphs". I thought that by default all objects > would display in the console their repr. The commit seems to indicate th

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Tuesday, 28 April 2015 21:17:43 UTC+1, Bill Page wrote: > > On 27 April 2015 at 23:52, Dima Pasechnik > > wrote: > > > > On Tuesday, 28 April 2015 02:27:21 UTC+1, Bill Page wrote: > >> > >> Yes you are right. The problem was in the original axiom.py. Here is a > >> patch that corrects th

[sage-devel] Re: Change of semantics for 'show'

I have read this thread, but I fail to understand the reason. Eg., there is a commit "extrawurst for graphs". I thought that by default all objects would display in the console their repr. The commit seems to indicate that this doesn't work for graphs. Why? Martin Am Mittwoch, 29. April 20

[sage-devel] Re: Change of semantics for 'show'

This is http://trac.sagemath.org/ticket/18289 On Wednesday, April 29, 2015 at 2:31:15 AM UTC-4, Martin R wrote: > > But then, why doesn't > > sage: graphs.PetersenGraph() > > output its repr and launches a viewer instead? Is this because, as yo

Re: [sage-devel] Re: Factoring p-adic polynomials

On 2015-04-28 20:59, Nils Bruin wrote: On Tuesday, April 28, 2015 at 11:25:07 AM UTC-7, Joao Alberto de Faria wrote: The problem is that this issue also occurs for R.=Qp(5)[] f=x^2 f.factor(), I was trying to fiddle with it and accidently copied the wrong code its trailing

Re: [sage-devel] Re: Factoring p-adic polynomials

You're right, thanks. David On Wed, Apr 29, 2015 at 6:11 AM, Jeroen Demeyer wrote: > There is no problem with reducible polynomials, only with non-squarefree > polynomials. The correct statement is: > > If your actual polynomial lies in the squarefree locus, it is possible to > increase precisio

Re: [sage-devel] Re: Factoring p-adic polynomials

There is no problem with reducible polynomials, only with non-squarefree polynomials. The correct statement is: If your actual polynomial lies in the squarefree locus, it is possible to increase precision enough so that a ball around it lies entirely within the squarefree locus. But if the ac

[sage-devel] Re: pynac may require C++11 in Sage

On 04/29/2015 08:01 AM, Thierry Dumont wrote: > Le 29/04/2015 02:28, Volker Braun a écrit : >> +1 to requiring C++11 support. >> >> IMHO that added a number of really nice refinements of the language, if >> you aren't using it yet for a C++ project then you are making a mistake. >> >> >> > > +1 >

[sage-devel] Please review ticket #18128 -- Face truncation of polyhedron

Hi, Please review #18128 . This ticket implements the method "face truncation" for polyhedron. The method "edge_truncation" is renamed simply "truncation". Thanks!!! Jean-Philippe -- You received this message because you are subscribed to the Google Grou

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

One thing could be to see how much of the information of the face lattice is required for some specific methods... Perhaps some of them could be implemented without using the face lattice in certain cases and be just as fast... -- You received this message because you are subscribed to the Goo

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

Hi, I had not noticed that Polyhedron created a Poset, and if so that 'makes > sense'. I had the same problem with both classes: it makes it very hard to > create a lot of Polyhedron objects, or many posets (and this, in turns, > makes it hard to write a routine that enumerates posets up to iso

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

Hello, Have a look at the thread Memory leak in Polyhedron object > > . > > Would that be the problem for you? In this case, the problem is the ticket > #14356. > I had no

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

Hi Nathann, Have a look at the thread Memory leak in Polyhedron object . Would that be the problem for you? In this case, the problem is the ticket #14356. Best, JP Le m