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

Am Mittwoch, 29. April 2015 02:12:50 UTC+2 schrieb Volker Braun: > > On Tuesday, April 28, 2015 at 12:35:57 PM UTC-4, Martin R wrote: >> >> So, plot(x) would have no side effect, instead I would have to call >> show() on the result? Slightly weird, but still OK for me. >> > > Not sure I underst

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

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 I am developing extensively in C++: C++11 offers many interesting i

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

+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. On Tuesday, April 28, 2015 at 4:23:25 AM UTC-4, Ralf Stephan wrote: > > Hello, > with C++11 unique_ptr in a pynac devel

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

On Tuesday, April 28, 2015 at 12:35:57 PM UTC-4, Martin R wrote: > > So, plot(x) would have no side effect, instead I would have to call show() > on the result? Slightly weird, but still OK for me. > Not sure I understand, so just to clarify: The current behavior is that plot() has no side effe

[sage-devel] Re: Introspection broken in Sage 6.6?

> > I think it's http://trac.sagemath.org/ticket/18249 > > > . > I think you're right, thanks. Nathan -- You received this message because you are subscribed t

Re: [sage-devel] Re: GSoC 2015: 5 projects funded

I'm adding my thanks to Harald. To the students: good luck, and have fun! On Tuesday, April 28, 2015 at 10:40:12 AM UTC-5, david@inria.fr wrote: > > > > On Tuesday, April 28, 2015 at 6:43:32 AM UTC+2, Vincent Knight wrote: >> >> Thanks for the hard work Harald and welcome to all the students!

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

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 the problem: >> >> https://github.com/billpage/sage/commit/237df92ef4e6b5117654f3a3ff7

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

See http://trac.sagemath.org/ticket/15422. Jeroen and I had a disagreement on what to do in this case, and ended up deciding that we should leave it as an ArithmeticError for now, pending more work on factoring. Brian Sinclair has a patch in progress at http://trac.sagemath.org/ticket/12561 imple

[sage-devel] Re: Introspection broken in Sage 6.6?

Nathan Dunfield wrote: > Dear all, > > In four different copies of Sage 6.6 on three different computers, I get > the below traceback whenever I try to do introspection. I tried > deleting ".sage" and ".ipython" but to no avail. I poked at it in pdb, > and the "object" argument at the last stage

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

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 > Right. That particular polynomial looks like it can't be co

[sage-devel] Introspection broken in Sage 6.6?

Dear all, In four different copies of Sage 6.6 on three different computers, I get the below traceback whenever I try to do introspection. I tried deleting ".sage" and ".ipython" but to no avail. I poked at it in pdb, and the "object" argument at the last stage is, as you would expect, the "b

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

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 On Tuesday, April 28, 2015 at 1:38:49 PM UTC-4, Nils Bruin wrote: > > On Tuesday, April 28, 2015 at 10:28:06 AM UTC-7, Joao Alberto de Faria > wrote:

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

On Tuesday, April 28, 2015 at 10:28:06 AM UTC-7, Joao Alberto de Faria wrote: > > What is the difficulty in factoring polynomials with multiple roots over > the p-adic ring? > > [[[ R.=Qp(5)[] > f=x^2 > g=gcd(f,f.derivative()) > (f/g).factor() ]]] > > returns the following error: > > sage.rings.

[sage-devel] Factoring p-adic polynomials

What is the difficulty in factoring polynomials with multiple roots over the p-adic ring? [[[ R.=Qp(5)[] f=x^2 g=gcd(f,f.derivative()) (f/g).factor() ]]] returns the following error: sage.rings.padics.precision_error.PrecisionError: p-adic factorization not well-defined since the discriminant

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

Ralf Stephan wrote: > On Tuesday, April 28, 2015 at 6:03:26 PM UTC+2, leif wrote: > > Anyway, IMHO each package should check whether C++11 is supported. > > > That may not be sufficient because headers from eg pynac are included > in cythonized files and so errors are generated there. When a

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

Am Dienstag, 28. April 2015 16:47:24 UTC+2 schrieb Volker Braun: > > Thats not really the topic but why not... > I'm sorry about having asked an off topic question. I did not realise that I did. > * view() should be renamed to something that is suggestive of what it > actually does, maybe p

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

On 28 April 2015 at 17:03, leif wrote: > On 04/28/2015 10:23 AM, Ralf Stephan wrote: >> So, is there any reason not to make C++11 mandatory in Sage? > > This probably "just" implies SAGE_INSTALL_GCC=yes on more platforms. > > Anyway, IMHO each package should check whether C++11 is supported. ecli

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

On Tuesday, April 28, 2015 at 6:03:26 PM UTC+2, leif wrote: > > Anyway, IMHO each package should check whether C++11 is supported. > That may not be sufficient because headers from eg pynac are included in cythonized files and so errors are generated there. When adding the C++11 switch to the com

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

On Tuesday, April 28, 2015 at 6:03:26 PM UTC+2, leif wrote: > > On 04/28/2015 10:23 AM, Ralf Stephan wrote: > > So, is there any reason not to make C++11 mandatory in Sage? > (We'd still have to deal with that in some extension modules' > extra_compile_args(?) for a while.) http://trac.sagema

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

On 04/28/2015 10:23 AM, Ralf Stephan wrote: > So, is there any reason not to make C++11 mandatory in Sage? This probably "just" implies SAGE_INSTALL_GCC=yes on more platforms. Anyway, IMHO each package should check whether C++11 is supported. (We'd still have to deal with that in some extension m

Re: [sage-devel] Re: GSoC 2015: 5 projects funded

On Tuesday, April 28, 2015 at 6:43:32 AM UTC+2, Vincent Knight wrote: > > Thanks for the hard work Harald and welcome to all the students! > +1 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

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

> * view() should be renamed to something that is suggestive of what it > actually does, maybe pdflatex(). +1 > * Add a warning (or deprecation) in show() to use pretty_print() instead as > it is more indicative of what it actually does. This is #18302 +1 > * Similar to latex(), there is a html()

[sage-devel] Re: sage-announce

> > > a. new release (release manager, currently Volker Braun), >> b. changelog (Jeroen Demeyer), >> c. tweaks to the changelog (Karl-Dieter Crisman), >> d. announcement (Harald Schilly). >> > > Actually, step c is > > c1. tweaks to the changelog (Karl-Dieter Crisman), > c2. new changelog with the

[sage-devel] Re: sage-announce

On 2015-04-28 16:05, Samuel Leličvre wrote: a. new release (release manager, currently Volker Braun), b. changelog (Jeroen Demeyer), c. tweaks to the changelog (Karl-Dieter Crisman), d. announcement (Harald Schilly). Actually, step c is c1. tweaks to the changelog (Karl-Dieter Crisman), c2. ne

[sage-devel] Re: sage-announce

I never posted to sage-announce... If we keep the process of manually editing the changelog then whoever makes the "final" version should send it to sage-announce (I guess that would be Karl-Dieter then). On Tuesday, April 28, 2015 at 10:19:38 AM UTC-4, Harald Schilly wrote: > > On Tue, Apr 28

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

On Tuesday, April 28, 2015 at 4:19:25 AM UTC-4, Martin R wrote: > > Could you please comment, what you'd like to change? > Thats not really the topic but why not... * view() should be renamed to something that is suggestive of what it actually does, maybe pdflatex(). In http://trac.sagemath.o

Re: [sage-devel] Re: developer map misaligned

I made this https://github.com/sagemath/website/issues/34 On Tuesday, April 28, 2015 at 10:36:24 AM UTC+2, Robert Bradshaw wrote: > > Looks like someone swapped the x and y coordinates. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To uns

[sage-devel] Re: sage-announce

On Tue, Apr 28, 2015 at 4:05 PM, Samuel Lelièvre wrote: > d. announcement (Harald Schilly). I'm not the one doing the announcements, I assume the release manager does it? But maybe we need someone else, especially because of b and c … where I never know for sure when the changelog-editing has fin

[sage-devel] sage-announce

Hi all, The announcements of Sage 6.4, Sage 6.4.1, Sage 6.5, Sage 6.6, did not make it to sage-announce. https://groups.google.com/forum/#!forum/sage-announce If I understand correctly, the workflow for new releases to get announced on sage-announce goes something like: a. new release (rele

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

Yo ! > this would mean that we will have to forbid the user to name them R. > This is ugly... Well, right now there is no defined constraint name and yet we have one in .show() Alternatively, when the users gives no constraint name, we could define the name to be "NobodyWouldChoseThisAsAConstrai

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

On 2015-04-28 14:22, kcrisman wrote: even make an alias for it? See http://trac.sagemath.org/ticket/13540 -- 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-de

[sage-devel] Re: GSoC 2015: 5 projects funded

> Thanks, Harald, > for the work making this possible. > >> >> +1! -- 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

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

> > > e.g. if your default solver is CPLEX then you'd doctest with >> > --optional=sage,cplex >> > and (ideally) should get no errors, etc. >> > >> >> It introduces complications since nobody (?) uses >> >> sage -tp --all --optional=xyz >> >> > I am using this (ok, call me nobody :-)) >

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

On Tuesday, 28 April 2015 12:56:57 UTC+1, Nathann Cohen wrote: > > Y ! > > > I mean that if I currently set the default solver to Gurobi, there are > few > > failing > > doctests, as Gurobi prints the LP a bit differently. > > An example: > > Oh, those Right :-P > > Perhaps

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

Y ! > I mean that if I currently set the default solver to Gurobi, there are few > failing > doctests, as Gurobi prints the LP a bit differently. > An example: Oh, those Right :-P Perhaps we could ' fix' them by saying in the gurobi backend that if a constraint is named R or som

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

On Tuesday, 28 April 2015 11:16:04 UTC+1, Nathann Cohen wrote: > > > Perhaps I was not clear enough: I meant to say: make the > solver-specific > > doctests work; we talk about a dozen doctests or so... > > > What do you mean by "make them work" ? We already have a lot of > solver-specific d

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

> Like I already said in a different post, the hard part is defining this: >> >> a reasonable base of optional packages. What about first trying with all of them, and see what happens? Most optional packages I am involved with just add a new feature. Some of them improve existing features, but the

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

Like I already said in a different post, the hard part is defining this: On 2015-04-26 21:55, Vincent Delecroix wrote: a reasonable base of optional packages. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and st

Re: [sage-devel] Re: failure in thematic_tutorials/linear_programming.rst with coin-or

> Perhaps I was not clear enough: I meant to say: make the solver-specific > doctests work; we talk about a dozen doctests or so... What do you mean by "make them work" ? We already have a lot of solver-specific doctests in the numerical/backends/ folder. Nathann -- You received this message

[sage-devel] sat review

Hi, if you care about SAT solving or memory leaks, could you review this one line patch? - del self +del self._solver http://trac.sagemath.org/ticket/18318 We never called the C++ destructor of the CryptoMiniSat class which means memleaks, big time. Cheers, Martin -- You

[sage-devel] Re: GSoC 2015: 5 projects funded

Thanks for giving me the opportunity to work on this project. Kind Regards, Tobenna Peter, Igwe On Monday, 27 April 2015 21:07:46 UTC+1, Harald Schilly wrote: > > Hello students and welcome to SageMath! This years GSoC funds five > projects: > > (Multivariate) Asymptotic Expressions > Benjamin

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

Latest NTL releases also require C++11. -- 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

Re: [sage-devel] Re: developer map misaligned

Looks like someone swapped the x and y coordinates. On Sun, Apr 26, 2015 at 12:52 PM, leif wrote: > Jan Groenewald wrote: >> Is it just me or do I seem to have moved somewhere West of Cape Verde in >> the Atlantic Ocean. The developer map developer locations are misaligned >> in both firefox and

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

Hello, with C++11 unique_ptr in a pynac develment version I get in Sage: gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/home/ ralf/sage/local/include -I/home/ralf/sage/src -I/home/ralf/sage/src/c_lib/include -I/home/ralf/sage/src/sage/ext -I/home/ralf/sage/local/lib/pytho

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

I set up some examples, together with output in emacs (sage mode), except for plot. Could you please comment, what you'd like to change? Except for plot, the results seem relatively consistent to me, but of course, this may be because I'm using the console. Thanks for your patience, Martin