#14149: Creation of temporary files with %attach
----------------------------------+-----------------------------------------
Reporter: aschilling | Owner: was
Type: defect | Status: needs_info
Priority: critical | Milestone: sage-5.10
Component: user interface | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Volker Braun | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by mstreng):
Replying to [comment:13 vbraun]:
> If that is the desired outcome then it would have been nice to doctest
it.
I tried to doctest tracebacks, but could not find a way (see #11812).
> Littering subdirectories with files in them into the file system is just
as bad as spewing random temp files into cwd. Temp files should go into
the sage temp directory.
Originally (before #7514 and again at #11812), temp directories *were*
used for the preparsed .py files. The location changed later. I don't know
when or why; maybe at #13579 because of security problems?
> Still, the correct fix is to make execution of in-memory code produce
correct tracebacks.
Yes, that would be best. Much better than my solution above, and much
better than what was done at #11812. But how? I would like to see the name
of the .sage file, and multi-line code snippets including line numbers.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14149#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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
