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
bar
> 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? Yo
As I was preparing to check-in my cross-compilation patch, which includes a
new x64 executable in the Lib/distutils/command directory, it occurs to me
that we don't actually need it in subversion - and nor do we need
wininst-9.0.exe.
I believe these executables are in svn for historical reasons.
>> Looks to me like the inittimezone function in timemodule.c should be
>> static.
Guido> Sounds like an oversight. Please fix!
Done. inittimezone is now declared static.
Skip
___
Python-Dev mailing list
[email protected]
http://mail.p
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
checking whether g++ also accepts flags for thread support...
> >"With TCP, we are never able to start multiple servers that bind
> > the same IP address and same port: a completely duplicate binding.
> > That is, we cannot start one server that binds 198.69.10.2 port 80
> > and start another that also binds 198.69.10.2 port 80, even if we
> > set the SO_REUS
On Apr 4, 2008, at 10:38 AM, Guido van Rossum wrote:
> On Fri, Apr 4, 2008 at 2:46 AM, Ralf Schmitt <[EMAIL PROTECTED]> wrote:
>> the news file for python 2.6 does not mention that you need to define
>> __hash__ in case you define __eq__ for a class.
>> This breaks some code (for me: mercurial and
Sounds like an oversight. Please fix!
On Fri, Apr 4, 2008 at 5:37 PM, <[EMAIL PROTECTED]> wrote:
>
> Looks to me like the inittimezone function in timemodule.c should be static.
> I don't see it called from any code other than within that module. If it's
> not supposed to be static it needs a
