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
On Friday, November 8, 2013 1:29:34 AM UTC-7, Nils Bruin wrote: > > On Thursday, November 7, 2013 11:20:53 PM UTC-8, Jeroen Demeyer wrote: >> >> On 2013-11-07 19:37, Nils Bruin wrote: >> > I can confirm that I also am not able to get "sage --python" to run >> > without printing a warning in any situation I tried where the current >> > directory is group writeable. >> You need either your umask to allow group-writing or you need to run >> python on a group-writable script or you need Python itself to be >> group-writable. But the scenario of the original poster of a "trusted" >> group indeed isn't supported, since there is no way for Python to know >> that that group is trusted. >> > > Ah thanks! Translating this into commands: > > $ umask 002 > $ sage -t ... > > should work. By setting your shell umask, you're informing python that you > consider groups safe. Do we have this documented anywhere? I wouldn't have > thought of 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.
