Guido van Rossum wrote:
>> There are also some issues that mainly crop up in non-English locales.
>> We will try to get to the bottom of those before releasing 3.0a2, but
>> I need help as I'm myself absolutely unable to work with locales (and
>> I don't have access to a Windows box).
>
> I think
Bill> I found that an SSL test was failing on 3K because of the following:
...
Bill> All of the modules in plat-mac are full of this kind of stuff.
ISTR much of the plat-mac stuff was generated by Tools/bgen. If so, that
would be the place to fix things.
Skip
___
> ISTR much of the plat-mac stuff was generated by Tools/bgen. If so, that
> would be the place to fix things.
Sure looks like generated code. Be nice if that generator was run
during the build process, on OS X. That way you'd be sure to get code
that matches the platform and codebase.
Bill
__
I'm seeing a sort of odd thing going on when running one of my tests.
I'm seeing two lines of output, from two different threads, being
duplicated when I run with "regrtest -u all -v test_ssl". This is
with the latest 3K sources on PPC OS X 10.4.10.
testSTARTTLS (test.test_ssl.ThreadedTests) ...
In the following, 'n' is equal to 0 (read from a non-blocking socket).
Is this a bug in the I/O module buffering?
Bill
Traceback (most recent call last):
File "/local/python/3k/src/Lib/SocketServer.py", line 222, in handle_request
self.process_request(request, client_address)
File "/local
More interesting is, what's b?
2007/10/27, Bill Janssen <[EMAIL PROTECTED]>:
> In the following, 'n' is equal to 0 (read from a non-blocking socket).
> Is this a bug in the I/O module buffering?
>
> Bill
>
> Traceback (most recent call last):
> File "/local/python/3k/src/Lib/SocketServer.py", li
Hard to say. Never seen this before. Are you using fork() *anywhere*
in your tests (not necessarily the affected test)?
2007/10/27, Bill Janssen <[EMAIL PROTECTED]>:
> I'm seeing a sort of odd thing going on when running one of my tests.
> I'm seeing two lines of output, from two different threads
I think the socket close in HTTPConnection.close() is incorrect, but is being
hidden by the delayed closing implemented in socket.py. See issue
1348.
Bill
___
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python
No, not unless the test harness uses it. But there are two threads.
> Hard to say. Never seen this before. Are you using fork() *anywhere*
> in your tests (not necessarily the affected test)?
>
> 2007/10/27, Bill Janssen <[EMAIL PROTECTED]>:
> > I'm seeing a sort of odd thing going on when runni
>From RawIOBase.read(). What's __index__() do?
b = bytes(n.__index__())
> More interesting is, what's b?
>
> 2007/10/27, Bill Janssen <[EMAIL PROTECTED]>:
> > In the following, 'n' is equal to 0 (read from a non-blocking socket).
> > Is this a bug in the I/O module buffering?
> >
> > Bi
10 matches
Mail list logo