[sage-devel] Re: Bug with vars()?

2015-05-26 Thread Volker Braun
I opened a ticket for the underlying issue: == Trac #18512: Move notebook() into Sage Right now the `notebook()` function is a lazy import from sagenb. Hence any access (like looking at the docstring) imports sagenb

[sage-devel] Re: Bug with vars()?

2015-05-06 Thread Volker Braun
There were some changes to how globals() are handled. Did you run make, can you show us the output, debugger, ... On Wednesday, May 6, 2015 at 10:51:27 AM UTC+2, Jean-Pierre Flori wrote: Dear all, My Sage 6.6 install quits after printing a depreciation warning message when I issue:

[sage-devel] Re: Bug with vars()?

2015-05-06 Thread leif
Jean-Pierre Flori wrote: My Sage 6.6 install quits after printing a depreciation warning message when I issue: sage: vars() Works for me: ... 'zeta': zeta, 'zeta__exact': function zeta__exact at 0x7fa3b8c84b90, 'zeta_symmetric': function zeta_symmetric at 0x7fa3bac2f9b0, 'zeta_zeros':

Re: [sage-devel] Re: Bug with vars()?

2015-05-06 Thread John Cremona
I also have a 6.6 install which quites badly when I give (as the first command) vars(). The output is hunderds of lines long and ends with TypeError Traceback (most recent call last) ipython-input-1-ef3ed5b882d8 in module() 1 vars()

Re: [sage-devel] Re: Bug with vars()?

2015-05-06 Thread John Cremona
On 6 May 2015 at 12:49, Volker Braun vbraun.n...@gmail.com wrote: vars() works as documented. Its a good test whether every object that we define can actually print That sounds like a good thing, but I still do not understand why an error is raised. John itself. That caughs up plenty of

Re: [sage-devel] Re: Bug with vars()?

2015-05-06 Thread Volker Braun
Technically its because * notebook is a lazy import, * printing notebook causes sagenb to be imported * which changes the displayhook to the SageNB displayhook which causes various problems. On Wednesday, May 6, 2015 at 1:58:45 PM UTC+2, John Cremona wrote: On 6 May 2015 at 12:49, Volker

Re: [sage-devel] Re: Bug with vars()?

2015-05-06 Thread Volker Braun
vars() works as documented. Its a good test whether every object that we define can actually print itself. That caughs up plenty of deprecation warnings and fails for sage: notebook sagenb.notebook.notebook_object.NotebookObject instance at 0x7fbf8537e758

Re: [sage-devel] Re: Bug with vars()?

2015-05-06 Thread Jean-Pierre Flori
I unpacked the sage 6.6 tarball and ran make. I'll have some trouble posting the exact output here as the machine is not connected to the network, but basically: * I'm on an amd64 Ubuntu 14.04.2 LTS. * I launch: sage * I type at Sage's prompt: vars() * I get: /blablabla/pretty_print.py:147:

Re: [sage-devel] Re: Bug with vars()?

2015-05-06 Thread Jeroen Demeyer
On 2015-05-06 14:09, Volker Braun wrote: Technically its because * notebook is a lazy import, * printing notebook causes sagenb to be imported * which changes the displayhook to the SageNB displayhook which causes various problems. I guess that's a bug. Simply *importing* sagenb should not