New submission from Étienne Buira :
With this patch, it raises an ArgumentException, instead of overwriting
previous subparser without notice.
Regards.
--
components: Library (Lib)
files: argparse_no_dup_subparsers.diff
keywords: patch
messages: 161112
nosy: eacb
priority: normal
New submission from Étienne Buira:
test_urllib2_localnet make non-explicit use of host configured http_proxy and
no_proxy, that will fail the test depending on their contents.
--
components: Tests
files: test_urllib2_localnet_proxy_conf.diff
keywords: patch
messages: 244901
nosy: eacb
New submission from Étienne Buira:
Amount of data the server could not send back is not a reliable indication on
how much data it received.
--
components: Tests
files: test_asynchat_check_received_len_if_received_len_matters.diff
keywords: patch
messages: 244922
nosy: eacb
priority
Étienne Buira added the comment:
Patch was for 2.7
Hunks about no_proxy are also relevant for other branches.
--
versions: +Python 3.2, Python 3.3, Python 3.4, Python 3.5
___
Python tracker
<http://bugs.python.org/issue24
Étienne Buira added the comment:
The issue is that this buffer is also emptied at the end.
Current version assumes that the server thread will not have enough opportunity
to send the whole buffer before receiving a RST.
But in reality, it's quite possible (happens reliably on a box) th
Changes by Étienne Buira :
Removed file:
http://bugs.python.org/file39643/test_asynchat_check_received_len_if_received_len_matters.diff
___
Python tracker
<http://bugs.python.org/issue24
Étienne Buira added the comment:
That would just race the other way around.
However, I missed the fact that the check of client's contents had no chance to
catch an issue, as the main thread were not entering asyncore.loop after
allowing the server to send.
Updated patch (agains
