On Sat, Apr 25, 2009 at 4:30 PM, Rado <rki...@gmail.com> wrote:
>
> Sweet, I will give it a shot.
>
> One last thing I noticed is that attached_files() is not exposed to
> the user. Again not sure if this is how its supposed to work or an
> actual bug. But if one can attach without refering to a library it
> would make sense to see what is currently attached again without extra
> work. Or at least the doc should be clearer on this. Here is what I
> mean:
>
> in command line:
> sage:attach test.py
> sage:attached_files() <---- fail, NameError: name 'attach_files' is
> not defined
> sage:sage.misc.interpreter.attached_files() <----works
>
> in notebook:
> sage:attach test.py
> sage:attached_files() <---- fail, AttributeError: 'module' object has
> no attribute 'attached_files'
> sage:w.attached_files() <--- this should work theoretically, once I
> figure out how to get a hold of the current worksheet and assign it to
> w. Any ideas?
>

attached_files *used* to be available on the command line.  Somebody
must have removed it.
Just add importing it back in misc/all_cmdline.py.    For the
notebook, the function
    sage.misc.interpreter.attached_files()
actually does *not* give the attached files, so don't add it to
all_notebook.py, unless it is fixed
to give the attached files.

William

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to