Opened 10 years ago

Last modified 10 years ago

#13963 closed defect

Failure running Sage when local/share/sage/ext doesn't exist — at Initial Version

Reported by: Jeroen Demeyer Owned by: Georg S. Weber
Priority: critical Milestone: sage-5.7
Component: build Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


It seems that nothing really guarantees the existence of the directory


apart from the installers of some packages.

When Sage is started when that directory doesn't exist:

[...lots of stuff...]
/release/merger/sage-5.7.beta0/local/lib/python2.7/site-packages/sage/interfaces/ in <module>()
      8 from expect import is_ExpectElement
----> 9 from gap import gap, gap_reset_workspace, gap_console, gap_version, set_gap_memory_pool_size, is_GapElement, Gap
     10 from gap3 import gap3, gap3_console, gap3_version, Gap3
     11 from genus2reduction import genus2reduction, Genus2reduction

/release/merger/sage-5.7.beta0/local/lib/python2.7/site-packages/sage/interfaces/ in <module>()
   1457 # if the modification time of the gap link has changed (which signals
   1458 # that gap has been somehow upgraded).
-> 1459 if not os.path.exists(WORKSPACE) or os.path.getmtime(WORKSPACE) < os.path.getmtime(GAP_STAMP):
   1460     #print "Automatically updating the cached Gap workspace:"
   1461     #print WORKSPACE

/release/merger/sage-5.7.beta0/local/lib/python/ in getmtime(filename)
     52 def getmtime(filename):
     53     """Return the last modification time of a file, reported by os.stat()."""
---> 54     return os.stat(filename).st_mtime

Change History (0)

Note: See TracTickets for help on using tickets.