On Wednesday, May 3, 2017 at 5:43:05 PM UTC-7, Jim Mooney wrote:
>
> I just wanted my own variables so this works. (I modified something I
> found on the web to delete all other values:
>
> G = globals()
> for k in G:
> if type(G[k]) == sage.symbolic.expression.Expression:
> if G[k]
I just wanted my own variables so this works. (I modified something I found
on the web to delete all other values:
G = globals()
for k in G:
if type(G[k]) == sage.symbolic.expression.Expression:
if G[k] not in [golden_ratio, NaN, I,
log2,pi,catalan,euler_gamma,twinprime, khinchin,
See #22941 for a separate approach (independent of #22933, each ticket
fixes a different problem).
John
On Tuesday, May 2, 2017 at 2:33:27 PM UTC-7, Dima Pasechnik wrote:
>
> this is now #22933, ready for review.
>
> Note that it's not a complete fix;
>
> sage: vars()
>
> still fails
>
>
this is now #22933, ready for review.
Note that it's not a complete fix;
sage: vars()
still fails
sage: v=vars()
sage: for k in v.keys(): print v[k]
works with the ticket branch.
On Tuesday, May 2, 2017 at 9:01:42 PM UTC+1, Dima Pasechnik wrote:
>
> In fact, complete_sandpile has been
In fact, complete_sandpile has been removed, but the lazy import for it is
still there.
So this has to be fixed. I will open a ticket.
On Tuesday, May 2, 2017 at 8:48:47 PM UTC+1, Dima Pasechnik wrote:
>
> no, it's more serious, perhaps something to do with lazy imports?
>
> sage: v=vars()
>
no, it's more serious, perhaps something to do with lazy imports?
sage: v=vars()
sage: v['complete_sandpile']
(I found the value of the guilty key by running
sage: for k in v.keys(): v[k]==None;
until it
Indeed, it appears that vars() is broken, and has been broken since Sage
7.5, at least.
Running
sage: vars()
ends with
---
TypeError Traceback (most recent call last)
in ()
> 1 vvv