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 change
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
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: D
On 6 May 2015 at 12:49, Volker Braun 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 deprecation warnings
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
---
TypeError
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)
in ()
> 1 vars()
/usr/local/sage/sage-2/local/lib/python2.7/site-packages/IP
