#17482: Fix load and save session in notebook
-------------------------------------+-------------------------------------
Reporter: kcrisman | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.5
Component: notebook | Resolution:
Keywords: | Merged in:
Authors: Karl-Dieter | Reviewers:
Crisman | Work issues:
Report Upstream: N/A | Commit:
Branch: | 7bc450bd0142af62e7393e6c65df25af365a901a
u/kcrisman/loadsavesagenb | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Changes (by kcrisman):
* status: needs_info => needs_review
Comment:
On the `save_session` side, you'll note that it already ''does'' save it
there. The problem is that this is '''only accessible from that cell'''
unless they saved it to the filesystem in a known location (with full
path, probably). And, frankly, not every sagenb user is sophisticated
enough to know what that means, and will just assume their file "is
there". Hence saving it somewhere universally accessible (in a given
worksheet). If one really had to, I guess if the path started with `/`
one could decide not to save it in `data/`.
I think it is far more likely that someone would do
{{{
save_session('foo') # in cell xyz
<quit notebook, play frisbee, have lunch>
<open notebook again>
load_session('foo') # in some other cell, perhaps directly below xyz, with
who knows what number
}}}
than that they will be asking for a specific filename on their computer.
And it's more convenient than having to remember some long path too -
again, anyone who actually knows what they are doing will not have a
problem with this anyway. But I rarely assume users, or myself, know what
they are doing.
I agree that one has to think about why the current code is there. But
given that the likely original author is the one who complained about it
'not working' in #9805, I am very reluctant not to consider this a bug!
And even William says there that the fix is just to figure out where
`data/` lives.
Anyway, if you don't want to give it positive review and leave that to
someone else, that's your prerogative, but I hope this clarifies why it's
reasonable to try to deal with this in the current fashion.
--
Ticket URL: <http://trac.sagemath.org/ticket/17482#comment:14>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.
