[sage-devel] Re: weird symbolic bug?

2015-03-30 Thread Ralf Stephan
> > See also > http://trac.sagemath.org/ticket/16587 > As suggested for that ticket (but not implemented atm whyever), addition of an _evalf_ method to the symbolic floor function resolves the problem. -- You received this message because you are subscribed to the Google Groups "sage-devel" g

[sage-devel] Re: weird symbolic bug?

2015-03-30 Thread Ralf Stephan
On Monday, March 30, 2015 at 9:57:14 AM UTC+2, Volker Braun wrote: > > Minimal testcase: > > sage: h(x) = floor(x) > sage: h(pi)._numerical_approx() > --- >4889 if is_a_numeric(x._gobj): > -> 4890 res =

Re: [sage-notebook] Re: [sage-devel] Sage Notebook shutdown

2015-03-30 Thread kcrisman
> > > 2. The following comment isn't necessarily very important in the > context of our discussion about sagenb, but it's worth making. I > think (based on data not just making things up) that most users of SMC > are unlikely to ever consider using Sage outside SMC. This is because > the maj

[sage-devel] Open Data Science Con

2015-03-30 Thread kcrisman
I don't know that I can justify going to this but it is tempting... several big Python things including the pandas author and author of Think Python. If there are a couple other Boston-area people who might be interested maybe we could go together. They *are* accepting "non-technical but da

[sage-devel] Re: Sage logo -- Proposal

2015-03-30 Thread kcrisman
I am pretty sure the current Sage logo is not an icosahedron - Harald can explain the exact provenance, I am sure. Count the edges and vertices etc. There are faces with four sides, for instance. -- You received this message because you are subscribed to the Google Groups "sage-devel" group.

Re: [sage-devel] Is it really a feature that sage_eval() doesn't access globals?

2015-03-30 Thread William Stein
On Mon, Mar 30, 2015 at 5:58 AM, Jeroen Demeyer wrote: > The documentation of sage_eval() seems to indicate that this is a feature: > > sage: a=5 > sage: sage_eval("a+1") > ... > NameError: name 'a' is not defined > > Of course you can do > > sage: a = 5 > sage: sage_eval("a+1", locals={'a':a}) >

Re: [sage-devel] Re: Sage Notebook shutdown

2015-03-30 Thread William Stein
On Mon, Mar 30, 2015 at 6:25 AM, Jason Grout wrote: > >> I just cracked open the users.pickle for sagenb, and found that there >> are 250443 total users. Of these, only 18688 (or 7.4%) actually have >> the email field set -- all others are blank. I guess these might be >> exactly the openid acc

[sage-devel] Re: Sage Notebook shutdown

2015-03-30 Thread Jason Grout
I just cracked open the users.pickle for sagenb, and found that there are 250443 total users. Of these, only 18688 (or 7.4%) actually have the email field set -- all others are blank. I guess these might be exactly the openid accounts. Of these, 15058 are gmail accounts, which are probably th

[sage-devel] Is it really a feature that sage_eval() doesn't access globals?

2015-03-30 Thread Jeroen Demeyer
The documentation of sage_eval() seems to indicate that this is a feature: sage: a=5 sage: sage_eval("a+1") ... NameError: name 'a' is not defined Of course you can do sage: a = 5 sage: sage_eval("a+1", locals={'a':a}) 6 But I'm wondering if sage_eval() with globals shouldn't "just work". The

[sage-devel] Re: Sage logo -- Proposal

2015-03-30 Thread john_perry_usm
On Sunday, March 29, 2015 at 11:07:10 AM UTC-5, Volker Braun wrote: > What IMHO is lacking is that it is too complicated. A *logo* is ideally > recognizable at 16x16px (e.g. favicon) and that pretty much excludes an > icosahedron. Its just too busy for that purpose. Maybe a tetrahedron would >

[sage-devel] Re: weird symbolic bug?

2015-03-30 Thread Volker Braun
Minimal testcase: sage: h(x) = floor(x) sage: h(pi)._numerical_approx() --- TypeError Traceback (most recent call last) in () > 1 h(pi)._numerical_approx() /home/vbraun/Code/sage.git/src/s

[sage-devel] Re: weird symbolic bug?

2015-03-30 Thread Eric Gourgoulhon
Hi, Le lundi 30 mars 2015 06:46:08 UTC+2, William a écrit : > > Hi, > > If I type > > sage: N(sqrt(floor(800*pi) - 1)) > > I get a number as expected. > > If I type > > sage: h(x) = (floor(8*pi*10^x)-1)^(1/2) > sage: a = h(10); a > sqrt(floor(800*pi) - 1) > > that seems f

[sage-devel] Re: help with conventions for python properties and __init__ question

2015-03-30 Thread 'Martin R' via sage-devel
> My initial reaction is that having such tricky behaviour is the wrong interface choice, so I'd recommend that you revisit your choice with that assumption and then see if you can convince yourself that you really do need `A(a) is a` to be True. OK, I found a different, simpler solution, as y