> and all starts working. I don't understand why and how I triggered it
> (e.g. how can this work in Sage?), but in any case, this is clearly a
> bug in pexpect.
Ok, it turns out it's not a bug in pexpect, but in the patch in pexpect.spkg:
$ cat patches/pexpect.py-isdir_bug_fix.diff
--- pexpect.py 2007-04-16 07:08:24.000000000 -0700
+++ ../../pexpect-2.0.p1.0/pexpect-2.0.p1/src/pexpect.py 2009-01-23
01:49:18.000000000 -0800
@@ -1130,7 +1130,7 @@
"""
# Special case where filename already contains a path.
if os.path.dirname(filename) != '':
- if os.access (filename, os.X_OK):
+ if os.access (filename, os.X_OK) and not os.path.isdir(f):
return filename
if not os.environ.has_key('PATH') or os.environ['PATH'] == '':
@@ -1145,7 +1145,7 @@
for path in pathlist:
f = os.path.join(path, filename)
- if os.access(f, os.X_OK):
+ if os.access(f, os.X_OK) and not os.path.isdir(f):
return f
return None
so it seems someone was fixing a bug and introduced a new bug.
Ondrej
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
