RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-September/009638.html below:

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

[Python-Dev] .pyc broken on Windows -- anywhere else? [Python-Dev] .pyc broken on Windows -- anywhere else?Tim Peters tim_one@email.msn.com
Thu, 28 Sep 2000 23:40:49 -0400

Previous message: [Python-Dev] .pyc broken on Windows -- anywhere else?
Next message: [Python-Dev] .pyc broken on Windows -- anywhere else?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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 ...

Previous message: [Python-Dev] .pyc broken on Windows -- anywhere else?
Next message: [Python-Dev] .pyc broken on Windows -- anywhere else?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4