[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2013-10-13 Thread Georg Brandl
Georg Brandl added the comment: It would appear so. -- nosy: +georg.brandl status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194 ___

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2013-02-06 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Should this issue be closed? -- nosy: +serhiy.storchaka status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194 ___

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-08 Thread Senthil Kumaran
Senthil Kumaran orsent...@gmail.com added the comment: py3k fixed in r87128 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194 ___ ___

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-07 Thread Arfrever Frehtes Taifersar Arahesis
Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com added the comment: Please also fix it in py3k branch in Lib/xmlrpc/client.py. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-06 Thread Dirkjan Ochtman
Dirkjan Ochtman dirk...@ochtman.nl added the comment: Can we get a decision on this? It's kind of sad that this regression wasn't fixed in 2.7.1. -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-06 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Even if the change may be straightforward, it requires a test. -- stage: - unit test needed versions: +Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-06 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: Kristjan, can you take a look? -- nosy: +krisvale ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194 ___

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-06 Thread Senthil Kumaran
Senthil Kumaran orsent...@gmail.com added the comment: I think, the file-like object behavior can be brought back. No need to handling gzipped file object in the patch, if the earlier behavior was not handling it. There is a separate issue to keep track of handling gzip encoded content in

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-06 Thread Kristján Valur Jónsson
Kristján Valur Jónsson krist...@ccpgames.com added the comment: The patch looks fine to me. If it runs and everyone is happy, by all means lets put it in. (I agree that the zlib stuff _should_ be handled elsewhere, but for reasons of expediency it was put into this module) --

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-06 Thread Senthil Kumaran
Senthil Kumaran orsent...@gmail.com added the comment: Instead of tossing around the GzipDecoding code from one method to another (which would in turn change the return value from those methods), I thought is appropriate to do a change in parse_response itself, so that it verifies that it is

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-06 Thread Senthil Kumaran
Senthil Kumaran orsent...@gmail.com added the comment: This issue is not applicable to release31-maint. -- resolution: - fixed versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-05 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194 ___

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-12-02 Thread Joshua Lock
Changes by Joshua Lock incandesc...@gmail.com: -- nosy: +joshual ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194 ___ ___ Python-bugs-list

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-10-28 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo, loewis, orsenthil ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8194 ___ ___

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-10-28 Thread Anthony Long
Anthony Long antl...@gmail.com added the comment: Patched my installation of python27 (via macports, snow leopard) and the patch was successful. Verified patch works in a limited capacity, using yolk. -- nosy: +antlong ___ Python tracker

[issue8194] Incompatible API change in xmlrpclib.Transport.parse_response() of Python 2.7 and 3.2

2010-03-26 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: In Python 2.6/3.1, xmlrpclib.Transport.parse_response() accepts a file like object. But Python 2.7/3.2 requires a HTTPResponse object because parse_response() calls response.getheader() method. The patch moves the call to