Why exception from os.path.exists()?

Dan Stromberg drsalists at gmail.com
Sat Jun 2 14:29:19 EDT 2018


On Sat, Jun 2, 2018 at 4:28 AM, Chris Angelico <rosuav at gmail.com> wrote:

> On Sat, Jun 2, 2018 at 9:13 PM, Steven D'Aprano
> <steve+comp.lang.python at pearwood.info> wrote:
> > On Sat, 02 Jun 2018 20:58:43 +1000, Chris Angelico wrote:
> Can someone confirm whether or not all the listed signals are actually
> supported? We know that Ctrl-C maps to the internal Windows interrupt
> handler, and "kill process" maps to the internal Windows "terminate",
> but can you send a different process all the different signals and
> handle them differently?
>
> I also can't find anything about path names there. What does POSIX say
> about the concept of relative paths? Does Windows comply with that?
>
> "Windows has some features which are compatible with the equivalent
> POSIX features" is not the same as "Technically, Windows is POSIX
> compliant".
>

The way I heard it, some (US government?) contracts required POSIX
compliance, so Microsoft added just enough of a mostly-useless POSIX layer
to Windows to be able to win the contracts, without actually being a useful
POSIX system.



More information about the Python-list mailing list