Repository navigation
xmlrpclib closes connection after each call #46348
Description
| BPO | 2076 |
|---|---|
| Nosy | @vstinner |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2009-09-14.10:44:32.561>
created_at = <Date 2008-02-12.11:04:08.767>
labels = ['type-feature', 'library']
title = 'xmlrpclib closes connection after each call'
updated_at = <Date 2009-09-14.10:44:32.559>
user = 'https://bugs.python.org/erno'bugs.python.org fields:
activity = <Date 2009-09-14.10:44:32.559>
actor = 'vstinner'
assignee = 'effbot'
closed = True
closed_date = <Date 2009-09-14.10:44:32.561>
closer = 'vstinner'
components = ['Library (Lib)']
creation = <Date 2008-02-12.11:04:08.767>
creator = 'erno'
dependencies = []
files = ['9414']
hgrepos = []
issue_num = 2076
keywords = []
message_count = 3.0
messages = ['62309', '64330', '92599']
nosy_count = 4.0
nosy_names = ['effbot', 'vstinner', 'erno', 'gpolo']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue2076'
versions = ['Python 2.5']
Activity
erno commentedon Feb 12, 2008
xmlrpclib is using the old HTTP and HTTPS classes from httplib which are
to quote the docstring, "Compatibility classes with httplib.py from 1.5."
and force the use of HTTP 1.0. This prevents connection reuse and
pipelining.
Attacked is some code we are using as a workaround.
Is the xmlrpclib in the standard library required to keep compatibility
with old python versions?
gpolo commentedon Mar 22, 2008
There is already a patch for using HTTP/1.1 in xmlrpclib:
http://bugs.python.org/issue1767370
There is also another open issue related to this, so the best to do here
is some "merging" of issues and patches and leave just one of them open.
vstinner commentedon Sep 14, 2009
I think that xmlrpclib is already fixed in Python trunk. See bpo-6267. I consider
this issue as a duplicate of bpo-6267.