Why exception from os.path.exists()?

Chris Angelico rosuav at gmail.com
Sat Jun 2 06:58:43 EDT 2018


On Sat, Jun 2, 2018 at 8:27 PM, Steven D'Aprano
<steve+comp.lang.python at pearwood.info> wrote:
> On Sat, 02 Jun 2018 10:32:55 +1000, Chris Angelico wrote:
>
>> On Sat, Jun 2, 2018 at 10:14 AM, Steven D'Aprano
>> <steve+comp.lang.python at pearwood.info> wrote:
>>>> But
>>>> assuming you're right, POSIX is still a set of minimum requirements -
>>>> not maximums, to my knowledge.
>>>
>>> It isn't even a set of minimum requirements. "<" is legal under POSIX,
>>> but not Windows.
>>
>> Windows isn't POSIX compliant.
>
> Technically, Windows is POSIX compliant. You have to turn off a bunch of
> features, turn on another bunch of features, and what you get is the bare
> minimum POSIX compliance possible, but it's enough to tick the check box
> for POSIX compliance.

Really? I didn't know that Windows path names were POSIX compliant. Or
do you have to use the Cygwin fudge to count Windows as POSIX? And
what about POSIX signal handling?

Citation needed, big-time.

ChrisA



More information about the Python-list mailing list