[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread Jason Grout
On 3/11/11 6:17 AM, Hector wrote: Hello everyone, I recently got my laptop formatted and hence have to work with older version of sage for few days.I cloned it and while starting the Sage I got following error. I have never been close to anything like this before so sorry but I am posting this

Re: [sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread Hector
Yes I do have a write permission to /home/hector/.sage//temp/ And that file looks like this - Netrw Directory Listing(netrw v136) /home/hector/.sage/temp Sorted by

[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread Jason Grout
On 3/11/11 7:22 AM, Hector wrote: Yes I do have a write permission to /home/hector/.sage//temp/ If you do have write permissions to that directory (*with* the double slash), then the double slash may not be the problem. And that file looks like this -

[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread kcrisman
If you do, then I bet that the problem is the double slash.  In fact, we just ran into this same sort of problem when working on the new jmol going into Sage---the temporary directory has a double-slash, so it is confusing where exactly that temp directory is. Incidentally, I've seen a lot

[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread John H Palmieri
On Friday, March 11, 2011 10:39:18 AM UTC-8, kcrisman wrote: If you do, then I bet that the problem is the double slash. In fact, we just ran into this same sort of problem when working on the new jmol going into Sage---the temporary directory has a double-slash, so it is confusing

Re: [sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread Robert Bradshaw
On Fri, Mar 11, 2011 at 11:39 AM, John H Palmieri jhpalmier...@gmail.com wrote: On Friday, March 11, 2011 10:39:18 AM UTC-8, kcrisman wrote: If you do, then I bet that the problem is the double slash.  In fact, we just ran into this same sort of problem when working on the new jmol going

[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread Volker Braun
Posix doesn't define the behaviour of double slashes. Most implementations treat it as single-slash, which is sane but clearly we shouldn't rely on benign behaviour. If you need to build a path, you should always use os.path.join. Not all OS'es understand slash as a path separator. -- To

[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread Volker Braun
Thats true if the multiple slashes are in the middle (though I agree that thats the case here). http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_11 say: A pathname that begins with two successive slashes may be interpreted in an implementation-defined manner,

[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread John H Palmieri
On Friday, March 11, 2011 11:46:05 AM UTC-8, Volker Braun wrote: If you need to build a path, you should always use os.path.join. +1. It would be good to fix parts of the Sage library which do otherwise. However, if you want to construct a URL (as in some of the scripts, like

[sage-devel] Re: Unexpected opening in Sage

2011-03-11 Thread Volker Braun
I'd say its safe to manually construct static paths. Whenever url components are specified by the user you should use urllib.quote() or similar to ensure validity. On Friday, March 11, 2011 8:12:23 PM UTC, John H Palmieri wrote: If you need to build a path, you should always use os.path.join.