Currently, it is quite hard to develop with the notebook. If 
https://github.com/sagemath/sagenb/pull/204 gets merged then it will be 
much easier. It will then be possible to create a symbolic link to the git 
repository and develop in the git repository; something like this:

$ cd SAGE_ROOT/local/lib/python/site-packages/sagenb-*
$ mv sagenb sagenb.original
$ ln -s /path/to/sagenb-github/sagenb sagenb

If I get some time, I will upgrade the documentation too.

 - basu.

On Monday, May 19, 2014 9:38:45 AM UTC+8, RJB wrote:
>
> I’ve been hoping that someone with greater skill would come along and save 
> the day by fixing defect 15308, but no luck. Attach files have not worked 
> in the notebook since version 5.10. I’ve tried my hand at figuring out what 
> is going on, but it is a problem specific to the notebook and debugging is 
> a challenge.  
>
> The only thing I can find about debugging in the notebook is 
> http://www.sagemath.org/doc/reference/cmd/sage/misc/trace.html, which 
> basically does a very good job describing how to debug sage in command 
> mode… and ends by pointing out that the method does not work with the 
> notebook. And I have confirmed this.
>
> Can anybody point me to a method of debugging the notebook? Even if it’s 
> just to tell me how to put print statements in and look at the results 
> somewhere, I’d be grateful.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to