[with patch, with positive review] .sage files destroy existing .py files
Reported by: |
jvoight |
Owned by: |
was |
Priority:
|
blocker
|
Milestone:
|
sage-2.10.1
|
Component:
|
interfaces
|
Keywords:
|
|
Cc:
|
|
Merged in:
|
|
Authors:
|
|
Reviewers:
|
|
Report Upstream:
|
N/A
|
Work issues:
|
|
Branch:
|
|
Commit:
|
|
Dependencies:
|
|
Stopgaps:
|
|
If files a.sage and a.py exist in a directory, then
sage: load a.sage
destroys the file a.py and replaces it with an automatically generated file. Either users should be warned of this "feature" or something else should be done.
Change History (12)
Milestone: |
sage-2.9 →
sage-2.8.11
|
Milestone: |
sage-2.9 →
sage-2.8.12
|
Milestone: |
sage-2.10 →
sage-2.9.2
|
Priority: |
minor →
blocker
|
Summary: |
.sage files destroy existing .py files →
[with patch, needs review] .sage files destroy existing .py files
|
Summary: |
[with patch, needs review] .sage files destroy existing .py files →
[with patch, with negative review] .sage files destroy existing .py files
|
Summary: |
[with patch, with negative review] .sage files destroy existing .py files →
[with patch, needs review] .sage files destroy existing .py files
|
Summary: |
[with patch, needs review] .sage files destroy existing .py files →
[with patch, with positive review] .sage files destroy existing .py files
|
Resolution: |
→ fixed
|
Status: |
new →
closed
|
Is there any reason to put the .py files in the same directory? It would probably be less confusing to just put them in temp. If one wants to see them, one can use sage -preparse.
I'm having trouble finding where exactly these files are getting written/used.