#11821: sage-preparse: give 'safer' names to .py files
--------------------------+-------------------------------------------------
Reporter: jhpalmieri | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: scripts | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author: John Palmieri
Merged: | Dependencies:
--------------------------+-------------------------------------------------
Comment(by leif):
I'd opt for either (2) or (3).
(3) is nicer from a user perspective, but ''may'' have other side effects.
(2) should be easy to implement (`try: import ...`), without potentially
breaking other code because of assumptions on the filename, so I tend to
prefer this variant.
[[BR]]
P.S.: Looks like the patch is not yet based on #9739. (Haven't tried.)
If we change the way `.sage` files are preparsed when doctesting, we might
run into errors due to left-over `<file>.py` files from `attach()` or
`load()`. Just a thought.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11821#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
