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
On 2013-11-08 09:29, Nils Bruin wrote:
Do we have this documented anywhere?
No. The place to document this would of course by Python. I personally
find it very unfortunate that upstream CPython seems to ignore this
issue. Perhaps my fix isn't perfect (as shown by this thread), but not
doing
On 2013-11-08, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2013-11-08 09:29, Nils Bruin wrote:
Do we have this documented anywhere?
No. The place to document this would of course by Python. I personally
find it very unfortunate that upstream CPython seems to ignore this
issue. Perhaps
On 2013-11-08 12:37, Dima Pasechnik wrote:
It might be that they want a platform-agnostic fix.
That's not the issue at all.
--
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
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
On Friday, November 8, 2013 9:53:06 AM UTC-7, Nils Bruin wrote:
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
On Friday, November 8, 2013 1:24:33 PM UTC-8, Nils Bruin wrote:
I think what you are experiencing can be characterized as a bug.
Hopefully someone can fix it or find a work-around.
In fact, I've just tried the same scenario on bsd.math.washington.edu,
which runs Darwin (so I guess OSX).
On Wednesday, November 6, 2013 10:27:53 PM UTC-7, Volker Braun wrote:
See http://trac.sagemath.org/ticket/13579#comment:40 and following...
On Wednesday, November 6, 2013 4:14:08 PM UTC-8, scma...@gmail.com
wrote:After our sysadmin updated the computer we use for a major project in
On Thursday, November 7, 2013 7:13:39 AM UTC-8, scma...@gmail.com wrote:
I read through that ticket before posting, but I didn't (and still don't)
see a solution to my problem. Admittedly I don't understand all of the
issues talked about on that ticket. I created a test script in the same
On Thursday, November 7, 2013 10:16:45 AM UTC-7, Nils Bruin wrote:
Your problem arises from the fact that sage's python is patched to be a
little more picky about permissions on paths.
How come this only comes into play for doctesting and not for just running
a script with sage? Using
On Thursday, November 7, 2013 10:01:00 AM UTC-8, scma...@gmail.com wrote:
How come this only comes into play for doctesting and not for just running
a script with sage? Using the example I posted before in the file
example_script.py, I get
It looks like sage silences the python message.
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
See http://trac.sagemath.org/ticket/13579#comment:40 and following...
On Wednesday, November 6, 2013 4:14:08 PM UTC-8, scma...@gmail.com wrote:
After our sysadmin updated the computer we use for a major project in Sage
from v5.3 to v5.12, our automated doctests stopped working. It appears to
13 matches
Mail list logo
