Changelog¶
Release 3.8.1 (2021-01-10)¶
- Dugong is now compatible with pytest 6.x and newer.
Release 3.8.0 (2020-11-09)¶
- Dugong now works under Windows.
Release 3.7.5 (2019-07-17)¶
- Fixed a deadlock when resuming coroutines.
- Made compatible with pytest 4.
Release 3.7.4 (2019-01-19)¶
- All traffic can now be dumped for debugging purposes using the
DUGONG_TRACEFILEenvironment variable. Make sure to include%dsomewhere in the filename - it will be replaced with a unique number to distinguish between different connections.
Release 3.7.3 (2018-04-29)¶
- Minor bugfixes.
Release 3.7.2 (2018-02-11)¶
- Now compatible with py.test 3.3
Release 3.7.1 (2017-06-05)¶
- Now compatible with Python 3.6.
Release 3.7 (2016-06-20)¶
- Dugong now supports server responses that specify just
Connection: closeinstead of providing the response length or using chunked encoding. - Dugong now honors the
check_hostnameattribute ofSSLContextobjects.
Release 3.6 (2016-04-23)¶
- Dugong now uses semantic versioning. This means that backwards-incompatible versions (i.e., versions that change the existing API in some way) will be reflected in an increase of the major version number, i.e. the next backwards-incompatible version will have version 4.0.
- Various minor bugfixes.
Release 3.5 (2015-01-31)¶
- The
is_temp_network_errorfunction now knows about more kinds of temporary errors, in particular also about those that do not have a corresponding Python exception (e.g. no route to host).
Release 3.4 (2014-11-29)¶
- The
examples/extract_links.pyscript is now Python 3.3 compatible again. - Dugong now has proper proxy support for plain HTTP connections. Thanks to Vincent Bernat for the patch.
- Dugong now raises
DNSUnavailableorHostnameNotResolvableexceptions instead of the more genericsocket.gaierrorandsocket.herrorexceptions where possible.
Release 3.3 (2014-08-06)¶
- It was possible for some methods to raise
BrokenPipeError, orConnectionResetErrorinstead ofConnectionClosed(especially under FreeBSD). This has now been fixed. - It was possible for methods that need to read data from the server
to raise
AssertionErrorin some circumstances. This has been fixed.
Release 3.2 (2014-07-27)¶
A
HTTPConnectioninstance can now be used as a context manager.If a connection is closed unexpectedly while request body data is being written to the server (i.e., during a call to
HTTPConnection.writeorHTTPConnection.co_write), dugong now pretends that the body has been sent to the server completely (while still raisingConnectionClosed).This makes it possible to catch the exception and nevertheless call
read_response(orco_read_response) to try to read an error response that the server may have sent during the upload (if no response has been received,ConnectionClosedwill be raised again).is_temp_network_errornow actively tries to distinguish between permanent and temporary name resolution problems by attempting to resolve a number of test hostnames.HTTPConnectionhas a newtimeoutattribute. RegularHTTPConnectionmethods (i.e., no coroutines) will now raiseConnectionTimedOutif no data could be send or received for timeout seconds.
Release 3.1 (2014-06-28)¶
- Fixed a problem with some testcases failing with a BrokenPipeError.
- Fixed a bug that, in some cases, resulted in additional
\0bytes being appended at the end of the response body, or in an incorrectInvalidResponseexception being raised. - When trying to continue reading or writing body data after calling
HTTPConnection.disconnect, dugong now raisesConnectionClosedinstead ofAttributeError.
Release 3.0, (2014-04-20)¶
- Major version bump because of backwards incompatible changes.
- Added
HTTPConnection.read_rawmethod. - The
PollNeededclass now uses theselect.POLLINandselect.POLLOUTconstants instead ofselect.EPOLLINandselect.EPOLLOUTto signal what kind of I/O needs to be performed. This makes dugong compatible with systems lacking epoll (e.g. FreeBSD). - The unit tests now check if the host is reachable before trying to run the example scripts. This avoids bogus test errors if there is no internet connection or if the remote host is down. (issue #7).
Release 2.2 (2014-03-14)¶
- Unittests requiring the
asynciomodule are now skipped if this module is not available.
Release 2.1 (2014-03-11)¶
- Fixed a problem where data was not sent to the server if the syscall was interrupted by a signal.
- It is no longer necessary to read from response body at least once even if has zero length.
PollNeeded.pollnow usesselect.pollinstead ofselect.select. This avoids a “filedescriptor out of range” exception that may be raised byselect.selectwhen the filedescriptor exceeds some system-specific value.
Release 2.0 (2014-02-23)¶
- Renamed module from httpio to dugong.
- The coroutine based API was completely overhauled.
- Introduced
BodyFollowingclass for use with body parameter ofsend_requestmethod. send_requestnow returns aHTTPResponseinstance instead of a tuple.- The
HTTPConnection.get_current_response()method has been removed. - The
HTTPConnection.fileno()method has been removed. - Added
CaseInsensitiveDictclass. send_requestnow converts the header parameter to aCaseInsensitiveDict.send_requestnow automatically generates aContent-MD5header when the body is passed in as a bytes-like object.HTTPConnection.readnow acceptsNonefor the len_ parameter.HTTPConnectioninstances now support a bare-bonesio.IOBaseinterface so that they can be combined withio.TextIOWrapperto read text response bodies.- The
HTTPConnection.close()method was renamed toHTTPConnection.disconnectto prevent confusion related to theclosedattribute (which may beTrueif the connection is established, but there is no active response body). - Repeatedly trying to read more response data after the response body
has been read completely no longer results in
StateErrorbeing raised, but simply returnsb''.
Release 1.0 (2013-07-13)¶
- Initial release.