So Martin fixed _ssl.c on Windows (thanks! what a subtle pit that
turned out to be), and I restored the test_timeout() test in
test_socket_ssl. That test was introduced on Bug Day, but:
a) First got fiddled to exclude Windows, because the _ssl.c bug made it
impossible for the test to pass on W
"Brett Cannon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> This should only apply to modules that want
> bugs reported outside of the Python tracker and have a separate dev
> track. People who just use the Python repository as their mainline
> version can just be left out.
If
Georg Brandl wrote:
> Suppose I wanted to implement that, what would be the best strategy
> to follow:
> - change handling of IMPORT_NAME and IMPORT_FROM in ceval.c
> - emit different bytecodes in compile.c
> - directly create TryExcept AST nodes in ast.c
I'd probably go for the third option. Isn
On Sat, 2006-04-08 at 14:47 -0700, Brett Cannon wrote:
> - email
This has an standalone release, but development and bug reports should
all happen in the Python project.
-Barry
signature.asc
Description: This is a digitally signed message part
___
P
OK, I am going to write the PEP I proposed a week or so ago, listing
all modules and packages within the stdlib that are maintained
externally so we have a central place to go for contact info or where
to report bugs on issues. This should only apply to modules that want
bugs reported outside of t
Georg Brandl wrote:
> A mailing list post found via Google suggests that Visual Studio automatically
> sets the struct member alignment to 4 bytes when building via old .mak files,
> for compatibility with older VC++.
Most likely, the poster didn't understand what's going on. I very much
doubt nma
Tim Peters wrote:
> _Perhaps_ it's the case that doubles are aligned to an 8-byte boundary
> when socketmodule.c is compiled, but (for some unknown reason) only to
> a 4-byte boundary when _ssl.c is compiled.
This is indeed what happens, because of what I consider three bugs:
one in Python, and tw
Michael Hudson wrote:
> "Tim Peters" <[EMAIL PROTECTED]> writes:
>
>> _Perhaps_ it's the case that doubles are aligned to an 8-byte boundary
>> when socketmodule.c is compiled, but (for some unknown reason) only to
>> a 4-byte boundary when _ssl.c is compiled. Although that seems to
>> match the
On Saturday 08 April 2006 1:05 am, Barry Warsaw wrote:
> On Sat, 2006-04-08 at 00:45 +0200, "Martin v. Löwis" wrote:
> > *Never* try to do i18n that way. Don't combine fragments through
> > concatenation. Instead, always use placeholders.
>
> Martin is of course absolutely right!
>
> > If you have
"Tim Peters" <[EMAIL PROTECTED]> writes:
> _Perhaps_ it's the case that doubles are aligned to an 8-byte boundary
> when socketmodule.c is compiled, but (for some unknown reason) only to
> a 4-byte boundary when _ssl.c is compiled. Although that seems to
> match the details in the bug report, I h
10 matches
Mail list logo
