On Tuesday, September 20, 2011 11:07:10 AM UTC-7, John H Palmieri wrote: > > If I create a simple Sage script and call it "script.sage", then running > "sage script.sage" works fine. But if I call it "new.sage", it doesn't. > Why? > > [snip]
> from twisted.python import util, context, reflect > File > "/Applications/sage/local/lib/python2.6/site-packages/Twisted-9.0.0-py2.6-macosx-10.6-i386.egg/twisted/python/util.py", > > line 5, in <module> > import os, sys, hmac, errno, new, inspect, warnings > I see, this is the problem: it's importing "new" here. Should "sage-preparse" name the preparsed file something safer, in order to prevent name clashes like this? For example, turn FILE.sage into FILE_preparsed.py? -- John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
