[sage-support] Why can't I see my code while debugging with trace?

2013-11-06 Thread Tobias Weich
Hi, If I load some sage script and try to debug it with trace I am unable to see the code which I'm debugging load('~/test.sage') trace('example_func()') yields only to an output like: ipdb s --Call-- string(2)example_func() ipdb s string(3)example_func() which is not very helpful. If I

[sage-support] Re: Why can't I see my code while debugging with trace?

2013-11-06 Thread Nils Bruin
On Wednesday, November 6, 2013 1:56:12 AM UTC-8, Tobias Weich wrote: Hi, If I load some sage script and try to debug it with trace I am unable to see the code which I'm debugging load('~/test.sage') trace('example_func()') yields only to an output like: ipdb s --Call--

[sage-support] Can't login to notebook

2013-11-06 Thread James Traynor
I have already sled this on Ask a Question and tried the following: Nothing seems to work. from sagenb.notebook.notebook import load_notebook nb = load_notebook(directory_to_run_sage_in) user_manager = nb.user_manager() user_manager.set_accounts(True) user_manager.add_user(username,

[sage-support] Error attaching file in notebook 5.12

2013-11-06 Thread stevemit
When I attach a simple .sage file in a notebook I get name 'Integer' is not defined. The notebook expression is: attach('/path/to/agcd.sage') The file contains: x=1 This works from the Sage command line. It fails in notebook each time I evaluate the expression. Sage version: 'Sage

[sage-support] Re: Error attaching file in notebook 5.12

2013-11-06 Thread kcrisman
On Wednesday, November 6, 2013 2:21:27 PM UTC-5, stevemit wrote: When I attach a simple .sage file in a notebook I get name 'Integer' is not defined. I think this is known. See for instance https://github.com/sagemath/sagenb/issues/169 - I feel like there was a Trac ticket as well, but

[sage-support] Running doctests in group writable directory

2013-11-06 Thread scmancuso
After our sysadmin updated the computer we use for a major project in Sage from v5.3 to v5.12, our automated doctests stopped working. It appears to be because the directory that contains our code is group writable (which makes sense because there are multiple users in our group who need to use

[sage-support] Re: Running doctests in group writable directory

2013-11-06 Thread Volker Braun
See http://trac.sagemath.org/ticket/13579#comment:40 and following... On Wednesday, November 6, 2013 4:14:08 PM UTC-8, scma...@gmail.com wrote: After our sysadmin updated the computer we use for a major project in Sage from v5.3 to v5.12, our automated doctests stopped working. It appears to

[sage-support] Re: Error attaching file in notebook 5.12

2013-11-06 Thread Volker Braun
Attach might have never worked in the notebook; there were no doctests for it. On Wednesday, November 6, 2013 1:14:05 PM UTC-8, kcrisman wrote: On Wednesday, November 6, 2013 2:21:27 PM UTC-5, stevemit wrote: When I attach a simple .sage file in a notebook I get name 'Integer' is not

[sage-support] Pb with shared notebooks

2013-11-06 Thread Laurent Decreusefond
Hi, I’ve Mavericks installed on my Mac. The compiled version of Sage 5.12 works perfectly (but I can’t compile it, it fails on polybori package). However, my main problem is not that one. I’m used to have my notebooks shared on a CloudMe folder. Precisely I’ve two Mac with both Mavericks and