Volker Braun wrote:
I'm against dicking around with HOSTNAME just in case it might be
invalid. This just leads to a maintenance nightmare where every script
that uses HOSTNAME needs to perform the same sanitation.
Well, depends on where it breaks (and why).
We have Python scripts that (should) use the value(s) from our env.py,
and shell scripts that (should usually) source sage-env.
So if we "sanitize" HOSTNAME etc. at all (or just bail out on invalid
settings), it should^TM be sufficient to do that in these two files.
Probably easier than changing all locations (mostly Python files setting
up / invoking shell commands I think) where we could run into trouble.
For starters, you just broke the sage cleaner again.
? I just quoted the changes that have been made.
-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.
