[Python-Dev] .pyc broken on Windows -- anywhere else?

[Tim Peters]

Nevermind.  Fixed it in a way that will be safe everywhere.

> -----Original Message-----
> From: python-dev-admin@python.org [mailto:python-dev-admin@python.org]On
> Behalf Of Tim Peters
> Sent: Thursday, September 28, 2000 11:41 PM
> To: Mark Favas; python-dev@python.org
> Subject: RE: [Python-Dev] .pyc broken on Windows -- anywhere else?
>
>
> Any Unix geek awake?  import.c has this, starting at line 640:
>
> #if defined(O_EXCL)&&defined(O_CREAT)&&defined(O_WRONLY)&&defined(O_TRUNC)
> ...
> 	fd = open(filename, O_EXCL|O_CREAT|O_WRONLY|O_TRUNC, 0666);
>
> I need to add O_BINARY to this soup to fix .pyc's under Windows.  Is
> O_BINARY customarily defined on Unices?  I realize Unices don't *need* it,
> the question is whether it will break Unices if it's there ...