I'd like to propose we delete Lib/Distutils/command/wininst-9.0.exe, and
enable the building of that project by default in the standard build process
(and I'll setup the x64 build of the executable similarly).
There are two issues here:
a) how does the binary get into the release tarball? You
I've reviewed the patch on http://bugs.python.org/issue815646 and have
uploaded my modified version (mostly test improvements and some formatting
to keep C code under 80 columns with proper 8 space tabs). I would have
committed it already but I have a sneaking suspicion that its unit test will
On Sat, Apr 5, 2008 at 9:17 PM, [EMAIL PROTECTED] wrote:
I just noticed this error message during configure:
checking whether gcc accepts -Olimit 1500... no
checking whether gcc supports ParseTuple __format__... no
checking whether pthreads are available without options... yes
As another alternative to providing a separate AMD64 binary, you could
also try to make the existing binary work properly on Win64, and tell
it with a config flag whether to look for Win32 or Win64 (or either)
on the target system.
I'm afraid that isn't an option for me in the short term.
Note the rm: conftest.dSYM: is a directory. This occurred a few
times during the configure process. Didn't cause it to conk out, but
is annoying.
Brett I am assuming this is on your OS X machine, Skip?
Yes, sorry. I forgot to mention that. As long as someone else sees it
As another alternative to providing a separate AMD64 binary, you could
also try to make the existing binary work properly on Win64, and tell
it with a config flag whether to look for Win32 or Win64 (or either)
on the target system.
I'm afraid that isn't an option for me in the short term.
Fixed in r62193.
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Trent Nelson [EMAIL
PROTECTED]
Sent: 04 April 2008 20:41
To: Martin v. Löwis
Cc: Christian Heimes; python-dev@python.org
Subject: Re: [Python-Dev] r62129 - in python/trunk:
I've attached a patch (http://bugs.python.org/file9966/trunk.2550.patch) to
issue 2550 that addresses the original problem here: test_support.bind_port()
potentially returning ports that have already been bound to. The patch updates
the tests that relied on this method, such that they call it
Note this message has been posted to numpy-discussion and python-dev.
Sorry for the multiple posting but I thought both python devs and
numpy users will be interested. If you believe your list should not
receive this email, let me know. Also I just wanted to introduce
myself since I may ask
