[issue9500] urllib2: Content-Encoding

R. David Murray added the comment: Issue 1508475 has a patch, though it still needs updated. -- resolution: -> duplicate stage: unit test needed -> committed/rejected status: open -> closed superseder: -> transparent gzip compression in liburl2 ___

[issue9500] urllib2: Content-Encoding

guest added the comment: Nah sorry, I've just been bothered to report it. As I don't run py3 can't write a patch anyway. And it wouldn't help for my current python 2.x setups also. I guess it's sufficient if this is googleable, and per-application workarounds are very much ok, as Python2 isn't

[issue9500] urllib2: Content-Encoding

R. David Murray added the comment: Thanks for the suggestion. New features can only go into Python3, where the urllib/urllib2 have been harmonized into the urllib package. So what we would need in order to consider this for acceptance is a patch against py3k trunk urllib. Please see http:/

[issue9500] urllib2: Content-Encoding

Changes by David Stanek : -- nosy: +dstanek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue9500] urllib2: Content-Encoding

New submission from guest : urllib2 doesn't support any real-world Content-Encoding scheme. "gzip" and "deflate" are standard compression schemes for HTTP and expected to be implemented by all clients. None of the default urllib2 handlers implements it. Common workarounds are available on the