[sage-devel] Where does this PolynomialRing error comes from?

2015-04-22 Thread Bruno Grenet
Salut ! While working on #5484, I encounter the following error messages, that I do not understand and am unable to track down: sage: B = QQ.quo(2) sage: R = PolynomialRing(B, 'x') Exception TypeError: "Argument 'other' has incorrect type (expected sage.structure.element.FieldElement, got int

Re: [sage-devel] Where does this PolynomialRing error comes from?

2015-04-22 Thread Jeroen Demeyer
On 2015-04-22 11:42, Bruno Grenet wrote: Salut ! While working on #5484, I encounter the following error messages, that I do not understand and am unable to track down: sage: B = QQ.quo(2) sage: R = PolynomialRing(B, 'x') Exception TypeError: "Argument 'other' has incorrect type (expected sage.

[sage-devel] Non-Sage C code in the Sage library

2015-04-22 Thread Jeroen Demeyer
Hello, The directory src/sage/graphs/planarity_c/ is really a copy of an external package https://code.google.com/p/planarity/ Similarly, src/sage/graphs/graph_decompositions/rankwidth_c is really a copy of http://pholia.tdi.informatik.uni-frankfurt.de/~philipp/software/rw.shtml What should we

[sage-devel] Re: Can't build Sage with 2GB RAM anymore

2015-04-22 Thread Volker Braun
On Wednesday, April 22, 2015 at 12:07:53 AM UTC-4, leif wrote: > > Hmmm, I also tried that yesterday (with SAGE_NUM_THREADS=8) but none of > the python processes was consuming more than 1 GB (in fact less) Same here. That is because 5gb / 8 < 1gb. But I'm pretty sure if you had only one process

[sage-devel] Re: Non-Sage C code in the Sage library

2015-04-22 Thread Jeroen Demeyer
I forgot to mention the C++ packages, the complete list of external code in Sage (AFAIK): src/sage/graphs/planarity_c/ https://code.google.com/p/planarity/ src/sage/graphs/graph_decompositions/rankwidth_c http://pholia.tdi.informatik.uni-frankfurt.de/~philipp/software/rw.shtml src/sage/schemes

[sage-devel] Re: Bad display of tuples in Sage 6.6 notebooks

2015-04-22 Thread Eric Gourgoulhon
Hi, Le vendredi 17 avril 2015 13:47:43 UTC+2, Volker Braun a écrit : > > Fixed in http://trac.sagemath.org/ticket/17821 (needs review) > > I've just tested it with Sage 6.7.beta2 (since it incorporates #17821): it works, both in Sage notebook and IPython notebook. Thank you! Eric. -- You rece

[sage-devel] Re: Non-Sage C code in the Sage library

2015-04-22 Thread Marc Mezzarobba
Jeroen Demeyer wrote: > src/sage/combinat/partitions_c.cc partitions_c could probably be replaced by the implementation in arb if people want to drop it. But having two implementations can be a good thing too... -- Marc -- You received this message because you are subscribed to the Google Gr

Re: [sage-devel] Re: Non-Sage C code in the Sage library

2015-04-22 Thread Martin Albrecht
On Wednesday 22 Apr 2015 14:10:51 Jeroen Demeyer wrote: > And then there are these, which seem to be external packages, but I > couldn't find a corresponding upstream: > > src/sage/stats/distributions/*.c Upstream (autotool-ised and all) is here: https://bitbucket.org/malb/dgs Cheers, Martin

Re: [sage-devel] Re: Non-Sage C code in the Sage library

2015-04-22 Thread Jeroen Demeyer
On 2015-04-22 14:21, Marc Mezzarobba wrote: Jeroen Demeyer wrote: src/sage/combinat/partitions_c.cc partitions_c could probably be replaced by the implementation in arb Why arb (which deals with floating point)? We already have 4 implementations in Sage to compute the number of partitions.

[sage-devel] Re: Re: Non-Sage C code in the Sage library

2015-04-22 Thread Marc Mezzarobba
Jeroen Demeyer wrote: >> partitions_c could probably be replaced by the implementation in arb > > Why arb (which deals with floating point)? Because arb has the best (fastest and most rigorous among the "fast" ones) implementation as far as I know. As for why Fredrik put it in arb, I guess that'

[sage-devel] typesetting problem in documentation

2015-04-22 Thread 'Martin R' via sage-devel
I just checked out develop and built it, without any trouble, EXCEPT, that the documentation isn't typeset properly. I am using Firefox 37.0.1 on kubuntu 14.04. I do not have this problem with sage 6.5 on this machine. Mathjax (I think) briefly displays a warning, which ends with File failed t

[sage-devel] Re: typesetting problem in documentation

2015-04-22 Thread Volker Braun
Works for me on sage-6.7.beta2 and firefox 37.0.1 I do get an error in the console: downloadable font: download failed (font-family: "MathJax_Blank" style:normal weight:normal stretch:normal src index:0): status=2147500037 source: about:blank in the console, but math still displays for me. Poss

[sage-devel] Re: typesetting problem in documentation

2015-04-22 Thread 'Martin R' via sage-devel
> We did upgrade mathjax recently. There is no hover menu, you need to right-click. Right-clicking shows no special menu. Looking at the html source, I see: Let \(R\) be a commutative ring. The (differential) Weyl algebra \(W\) is the algebra generated by \(x_1, x_2, \ldots x_n, \partial_{x_1

[sage-devel] Re: typesetting problem in documentation

2015-04-22 Thread Volker Braun
Is that an upgrade from earlier sage versions? Upgrade to ensure that the re is no old mathjax lying around. sage -f mathjax make doc-clean make doc On Wednesday, April 22, 2015 at 11:12:22 AM UTC-4, Martin R wrote: > > > We did upgrade mathjax recently. There is no hover menu, you need to > r

[sage-devel] Re: Issues with GCC 5.x

2015-04-22 Thread leif
On 04/22/2015 05:30 AM, leif wrote: > Release of GCC 5.1 is scheduled for Wednesday, April 22nd. It's out now: https://gcc.gnu.org/ml/gcc/2015-04/msg00287.html The errors with ncurses and gf2x remain. 8-/ -leif > I took the first release candidate and tried to build Sage 6.6 with it: > >

[sage-devel] Re: Can't build Sage with 2GB RAM anymore

2015-04-22 Thread leif
On 04/22/2015 02:05 PM, Volker Braun wrote: > On Wednesday, April 22, 2015 at 12:07:53 AM UTC-4, leif wrote: > > Hmmm, I also tried that yesterday (with SAGE_NUM_THREADS=8) but none of > the python processes was consuming more than 1 GB (in fact less) > > > Same here. That is because 5gb

[sage-devel] Evaluating algebraic polynomials on symbolic expressions

2015-04-22 Thread Marc Mezzarobba
Currently, evaluating a polynomial ring element on a symbolic expression returns a result in Horner form: sage: pol = QQ['x'](range(10)) sage: pol(x) 9*x + 8)*x + 7)*x + 6)*x + 5)*x + 4)*x + 3)*x + 2)*x + 1)*x This behavior is of course a side effect of the default generic evaluation al

[sage-devel] Re: typesetting problem in documentation

2015-04-22 Thread 'Martin R' via sage-devel
> Is that an upgrade from earlier sage versions? Upgrade to ensure that the re is no old mathjax lying around. no. all completely fresh. However, there is a sage (my production sage :-) in the path, might that be a problem? Thanks, Martin -- You received this message because you are subscr

Re: [sage-devel] Evaluating algebraic polynomials on symbolic expressions

2015-04-22 Thread Vincent Delecroix
On 22/04/15 19:48, Marc Mezzarobba wrote: Currently, evaluating a polynomial ring element on a symbolic expression returns a result in Horner form: sage: pol = QQ['x'](range(10)) sage: pol(x) 9*x + 8)*x + 7)*x + 6)*x + 5)*x + 4)*x + 3)*x + 2)*x + 1)*x This behavior is of course a side e

Re: [sage-devel] Non-Sage C code in the Sage library

2015-04-22 Thread Michael Orlitzky
On 04/22/2015 07:57 AM, Jeroen Demeyer wrote: > Hello, > > The directory > src/sage/graphs/planarity_c/ > is really a copy of an external package > https://code.google.com/p/planarity/ > > Similarly, > src/sage/graphs/graph_decompositions/rankwidth_c > is really a copy of > http://pholia.tdi.info

[sage-devel] Re: typesetting problem in documentation

2015-04-22 Thread Volker Braun
Shouldn't be a problem, though maybe you can try without and report back... On Wednesday, April 22, 2015 at 1:51:30 PM UTC-4, Martin R wrote: > > > Is that an upgrade from earlier sage versions? Upgrade to ensure that > the re is no old mathjax lying around. > > no. all completely fresh. Howeve

Re: [sage-devel] Evaluating algebraic polynomials on symbolic expressions

2015-04-22 Thread Nils Bruin
On Wednesday, April 22, 2015 at 11:02:52 AM UTC-7, vdelecroix wrote: > Definitely! A side effect of the current behavior > > sage: p = ZZ['x'](range(5)) > sage: f = sum(i*x**i for i in range(5)) > sage: str(p) == str(f) > True > sage: p == f > (((4*x + 3)*x + 2)*x + 1)*x == 4*x^4 + 3*x^3 + 2

[sage-devel] a patchbot named eddy

2015-04-22 Thread Frédéric Chapoton
Hello, This patchbot is running version 2.2, which has several disadvantages, in particular it uses the master branch as a base. This means that it only works nicely when "develop" is not a beta but a release... Not so often, so to say. So, please, upgrade to patchbot 2.3.3, available here: sa

[sage-devel] Re: Can't build Sage with 2GB RAM anymore

2015-04-22 Thread leif
On 04/21/2015 11:57 PM, Andrey Novoseltsev wrote: > It is a single core single thread 64-bit CPU (Athlon 64M), suggestions > to use USB 3/PCIe SSD are funny but miss the point: for no apparent gain > systems that were capable of building Sage can't do it anymore (or > require tweaking to reduce par

[sage-devel] Re: Can't build Sage with 2GB RAM anymore

2015-04-22 Thread Volker Braun
I wouldn't want another environment variable for that. If we have to, chunking at 10 would be fine. Though ideally this would be dealt with on the cython side, I made a post here: https://groups.google.com/d/msg/cython-users/7UoMj84Y5os/6UAXi64MA88J On Wednesday, April 22, 2015 at 6:04:41 PM U

[sage-devel] Re: Can't build Sage with 2GB RAM anymore

2015-04-22 Thread Volker Braun
PS: The script for plotting cpu/mem usage is now at https://github.com/vbraun/GraphPG -- 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...@goog

[sage-devel] Re: Can't build Sage with 2GB RAM anymore

2015-04-22 Thread leif
On 04/23/2015 03:36 AM, Volker Braun wrote: > I wouldn't want another environment variable for that. Well, easier for playing than editing the sources... ;-) A good default value should be chosen automatically. > If we have to, > chunking at 10 would be fine. I think it's ok for machines with 2

[sage-devel] Re: typesetting problem in documentation

2015-04-22 Thread 'Martin R' via sage-devel
Indeed, no change. I installed konqueror, where things work. So it is a firefox problem... -- 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...