v0.2.0

Major Changes

• Python 2.7.9 is now fully supported. ⭐ 🍰

v0.1.2

Minor Changes

• We now remove the Connection header if it's given to us, as that header
  is not valid in HTTP/2.

Bugfixes

• Adds workaround for HTTPie to make our responses look more like urllib3
  responses.

v0.1.1

Minor Changes

• Support for HTTP/2 draft 15, and 16. No drop of support for draft 14.
• Updated bundled certificate file.

Bugfixes

• Fixed AttributeError being raised when a PING frame was received, thanks
  to @t2y. (Issue #79)
• Fixed bug where large frames could be incorrectly truncated by the buffered
  socket implementation, thanks to @t2y. (Issue #80)

v0.1.0

Changes

Regressions and Known Bugs

• Support for Python 3.3 has been temporarily dropped due to features missing
  from the Python 3.3 ssl module. PyOpenSSL has been identified as a
  replacement, but until NPN support is merged it cannot be used. Python 3.3
  support will be re-added when a suitable release of PyOpenSSL is shipped.
• Technically this release also includes support for PyPy and Python 2.7. That
  support is also blocked behind a suitable PyOpenSSL release.

For more information on these regressions, please see issue #37.

Major Changes

• Support for HPACK draft 9.
• Support for HTTP/2 draft 14.
• Support for Sever Push, thanks to @alekstorm. (Issue #40)
• Use a buffered socket to avoid unnecessary syscalls. (Issue #56)
• If nghttp2 is present, use its HPACK encoder for improved speed and
  compression efficiency. (Issue #60)
• Add HTTP20Response.gettrailer() and HTTP20Response.gettrailers(),
  supporting downloading and examining HTTP trailers. (Discussed in part in
  Issue #71.)

Bugfixes

• HTTP20Response objects are context managers. (Issue #24)
• Pluggable window managers are now correctly informed about the document size.
  (Issue #26)
• Header blocks can no longer be corrupted if read in a different order to the
  one in which they were sent. (Issue #39)
• Default window manager is now smarter about sending WINDOWUPDATE frames.
  (Issue #41 and Issue #52)
• Fixed inverted window sizes. (Issue #27)
• Correct reply to PING frames. (Issue #48)
• Made the wheel universal, befitting a pure-Python package. (Issue #46)
• HPACK encoder correctly encodes header sets with duplicate headers.
  (Issue #50)

Distributions

V0.1.0 of hyper can be installed from pip. Alternatively, you can download any of the distributions from this release. Download a .tar.gz file if you're on a Unix OS, a .zip file on Windows, or the wheel (.whl) file on any OS. The .asc files are signed using my GPG key from Keybase.

v0.0.4

Changes

• Add logic for pluggable objects to manage the flow-control window for both
  connections and streams.
• Raise new HPACKDecodingError when we're unable to validly map a
  Huffman-encoded string.
• Correctly respect the HPACK EOS character.

Distributions

V0.0.4 of hyper can be installed from pip. Alternatively, you can download any of the distributions from this release. Download a .tar.gz file if you're on a Unix OS, a .zip file on Windows, or the wheel (.whl) file on any OS. The .asc files are signed using my GPG key from Keybase.

v0.0.3

• Use bundled SSL certificates in addition to the OS ones, which have limited
  platform availability. (#9)
• Connection objects reset to their basic state when they're closed, enabling
  them to be reused. Note that they may not be reused if exceptions are thrown
  when they're in use: you must open a new connection in that situation.
• Connection objects are now context managers. (#13)
• The HTTP20Adapter correctly reuses connections.
• Stop sending WINDOWUPDATE frames with a zero-size window increment.
• Provide basic functionality for gracelessly closing streams.
• Exhausted streams are now disposed of. (#14)

v0.0.2

• Implemented logging. (Issue #12)
• Stopped HTTP/2.0 special headers appearing in the response headers. (Issue #16)
• HTTP20Connection objects are now context managers. (Issue #13)
• Response bodies are automatically decompressed. (Issue #20)
• Provide a requests transport adapter. (Issue #19)
• Fix the build status indicator. (Issue #22)