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.pyt...@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. What what of it? POSIX is not a minimum set of requirements for Python. POSIX is a set of standards that describes how Linux/Unix/MacOS systems are expected to behave. Adhering to the POSIX standard isn't a requirement for Python. > Anyhow, I've come to the conclusion that we're all about equally wrong > here To paraphrase Isaac Asimov, "People who say the earth is flat are wrong, and people who say the earth is a sphere are wrong, but if you say that those two groups of people are equally wrong, you are more wrong than both of them put together." -- Steven D'Aprano "Ever since I learned about confirmation bias, I've been seeing it everywhere." -- Jon Ronson -- https://mail.python.org/mailman/listinfo/python-list
