On Friday, November 8, 2013 6:56:54 AM UTC-8, [email protected] wrote: > > That makes sense, but it didn't work for me: > > $ umask 002 > $ umask > 0002 > $ sage -t example_script.py > Traceback (most recent call last): > ... > RuntimeError: refusing to run doctests from the current directory > '/DIR1/DIR2' since untrusted users could put files in this directory, > making it unsafe to run Sage code from > Hm, would you mind posting the results of:
$pwd and then the permissions of all components, e.g.: if it's /home/user/sage $ ls -dl /home $ ls -dl /home/user $ ls -dl /home/user/sage $ ls -dl /home/user/sage/example_script.py $ ls -dl `which sage` You can apply some bijective map to the UIDs, GIDs, and directory names if you think that's required. You might also want to see what kind of file system is mounted for this. I think there are network file systems that keep track of permissions via ACL and return garbage for unix permissions. That would definitely throw off Jeroen's heuristic (and problems like this is why the python devs are so reluctant to include a change like this) -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
