The OpenBSD buildbot always fail with the same failures since many
months (ex: test_socket). Is someone interested to fix them? If no,
would it be possible to turn it off to get a better view of
regressions? Currently, they are too many red buildbots to quickly see
regressions introduced by recent commits.
I have opened an enhancement request (23830) with a suggested path that
adds support for the AF_IUCV protocol family:
IUCV is a hypervisor mediated communications method for z/VM guest virtual
machines. Linux on z Systems (aka s390x) has supported this via the use of
AF_IUCV sockets for many years (added to kernel Feb 2007). This suggested
patch adds support to Python 2.7.9 for this socket type. I have built
Python on both s390x and x86_64: both build cleanly and the test added to
test_socket.py runs cleanly on s390x and is skipped on other platforms.
components: Library (Lib)
title: Add AF_IUCV support to sockets
versions: Python 2.7
Added file: http://bugs.python.org/file38765/af_iucv.patch
I would like help in improving the patch and making it a candidate for
acceptance into the code base.
I'm not sure whether this should be python-list or here, but given it's a premature code review for http.client, I figured I'd post here first.
I'm in the process of adding support for chunked transfer encoding to http.client (issue #12319). One of the bits of functionality that I'm working on in is ironing out some of the kinks out in determining the content length of the request bodies. Given the number of data types allowed as bodies it does get a little messy, so I wanted to get some feedback here and see if anyone can shoot holes through it prior to updating the current patch. The tests are passing, but there may be use cases not accounted for in the new implementation.
The above is intended to replace _set_content_length (current state of the patch can be seen here: http://bugs.python.org/review/12319/diff/14331/Lib/http/client.py). There is a comprehensive list of data types currently supported can be found here: http://bugs.python.org/issue23740. Comments and feedback are much appreciated.
The buildbot AMD64 OpenIndiana 3.x is always red since at least 6
months. Almost always, tests fail because the buildbot has not enough
memory. Well, it's fun to see how Python handles MemoryError (it's
pretty good, there is no hard crash! my work on failmalloc was maybe
useful ;-)), but it doesn't help to detect regressions.
Would it be possible to enhance this buildbot?
I copy this email to the owner of buildbot. But I also sent it to
python-dev because MemoryError is not the only error, please take care
of our buildbots!