Volker Braun wrote:
On Monday, June 3, 2013 8:47:17 AM UTC+1, leif wrote:
Worth a ticket?
Not sure; Apparently OSX does escape illegal characters usually, though
clearly some people get bitten by this. Might be dependent on whether
the name was entered during installation / upgraded from previous versions.
A more worthy goal would be to fix escaping in associated command line
scripts in Sage. It shouldn't be a problem to have space / assorted UTF8
in your home directory name. There, setting HOSTNAME to something
invalid would actually be useful for testing.
I rather meant
# for backwards compatiblity
from sage.env import *
LOCAL_IDENTIFIER = '%s.%s'%(HOSTNAME , os.getpid())
(in misc.py) which is used for the "unique" temporary directory name,
SAGE_TMP (which here was the problem); this is a slight regression since
we already did some substitutions for HOSTNAME (env.py no longer does):
-HOSTNAME =
socket.gethostname().replace('-','_').replace('/','_').replace('\\','_')
+# for backwards compatiblity
+from sage.env import *
env.py copies verbatim:
_add_variable_or_fallback('UNAME', os.uname()[0])
_add_variable_or_fallback('HOSTNAME', socket.gethostname())
_add_variable_or_fallback('LOCAL_IDENTIFIER','$HOSTNAME.%s'%os.getpid())
Special characters in filenames in general (including $DOT_SAGE) are
another issue.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
