Why no isexec, isread, iswrite, etc (was: I must be missing something obvious: os.path.isexecutable?)

[Darren New]

> > One possibility is that there's more than one answer to the question
> > of "isexec" - it's not a single bit, but one that can exist for all of
> > owner, group and world.

UNIX has ACLs now almost as sophisticated as NT does, too.
 
> Another possibility is that "isexec" isn't a portable concept... 
> How would you implement it on Windows, for example?

Anything you have execute permission for? 

What if the machine is down and it's on a network-mounted mount point? What
if the path after the #! doesn't exist, or isn't executable.

Try executing the file and see if you get what you want. That's "isexec".
:-)

-- 
Darren New / Senior MTS & Free Radical / Invisible Worlds Inc.
San Diego, CA, USA (PST).  Cryptokeys on demand.
"It says this wine has syphilis."
               "I think that's pronounced `sulphates'."