---
- branch: MAIN
  date: Wed Apr 20 16:10:14 UTC 2016
  files:
  - new: '1.2'
    old: '1.1'
    path: pkgsrc/www/py-h2/Makefile
    pathrev: pkgsrc/www/py-h2/Makefile@1.2
    type: modified
  - new: '1.2'
    old: '1.1'
    path: pkgsrc/www/py-h2/distinfo
    pathrev: pkgsrc/www/py-h2/distinfo@1.2
    type: modified
  - new: '1.2'
    old: '1.1'
    path: pkgsrc/www/py-h2/patches/patch-setup.py
    pathrev: pkgsrc/www/py-h2/patches/patch-setup.py@1.2
    type: modified
  id: 20160420T161014Z.92300531a763f6aa2f9bc6548deccae749f7504b
  log: "Update www/py-h2 to 2.2.3\n\nChanges:\n2.2.3 (2016-04-13)\n------------------\nBugfixes\n~~~~~~~~\n-
    Allowed the 4.X series of hyperframe releases as dependencies.\n\n2.1.4 (2016-04-13)\n------------------\nBugfixes\n~~~~~~~~\n-
    Allowed the 4.X series of hyperframe releases as dependencies.\n\n2.2.2 (2016-04-05)\n------------------\nBugfixes\n~~~~~~~~\n-
    Fixed issue where informational responses were erroneously not allowed to be\n
    \ sent in the ``HALF_CLOSED_REMOTE`` state.\n- Fixed issue where informational
    responses were erroneously not allowed to be\n  received in the ``HALF_CLOSED_LOCAL``
    state.\n- Fixed issue where we allowed information responses to be sent or received\n
    \ after final responses.\n\n2.2.1 (2016-03-23)\n------------------\nBugfixes\n~~~~~~~~\n-
    Fixed issue where users using locales that did not default to UTF-8 were\n  unable
    to install source distributions of the package.\n\n2.2.0 (2016-03-23)\n------------------\nAPI
    Changes (Backward-Compatible)\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n- Added support
    for sending informational responses (responses with 1XX status)\n  codes as part
    of the standard flow. HTTP/2 allows zero or more informational\n  responses with
    no upper limit: hyper-h2 does too.\n- Added support for receiving informational
    responses (responses with 1XX\n  status) codes as part of the standard flow. HTTP/2
    allows zero or more\n  informational responses with no upper limit: hyper-h2 does
    too.\n- Added a new event: ``ReceivedInformationalResponse``. This response is
    fired\n  when informational responses (those with 1XX status codes).\n- Added
    an ``additional_data`` field to the ``ConnectionTerminated`` event that\n  carries
    any additional data sent on the GOAWAY frame. May be ``None`` if no\n  such data
    was sent.\n- Added the ``initial_values`` optional argument to the ``Settings``
    object.\n\nBugfixes\n~~~~~~~~\n- Correctly reject all of the connection-specific
    headers mentioned in RFC 7540\n  å\x89\x87 8.1.2.2, not just the ``Connection:``
    header.\n- Defaulted the value of ``SETTINGS_MAX_CONCURRENT_STREAMS`` to 100,
    unless\n  explicitly overridden. This is a safe defensive initial value for this\n
    \ setting.\n\n2.1.3 (2016-03-16)\n------------------\nDeprecations\n~~~~~~~~~~~~\n-
    Passing dictionaries to ``send_headers`` as the header block is deprecated,\n
    \ and will be removed in 3.0.\n\n2.1.2 (2016-02-17)\n------------------\nBugfixes\n~~~~~~~~\n-
    Reject attempts to push streams on streams that were themselves pushed:\n  streams
    can only be pushed on streams that were initiated by the client.\n- Correctly
    allow CONTINUATION frames to extend the header block started by a\n  PUSH_PROMISE
    frame.\n- Changed our handling of frames received on streams that were reset by
    the\n  user.\n  Previously these would, at best, cause ProtocolErrors to be raised
    and the\n  connection to be torn down (rather defeating the point of resetting
    streams\n  at all) and, at worst, would cause subtle inconsistencies in state
    between\n  hyper-h2 and the remote peer that could lead to header block decoding
    errors\n  or flow control blockages.\n  Now when the user resets a stream all
    further frames received on that stream\n  are ignored except where they affect
    some form of connection-level state,\n  where they have their effect and are then
    ignored.\n- Fixed a bug whereby receiving a PUSH_PROMISE frame on a stream that
    was\n  closed would cause a RST_STREAM frame to be emitted on the closed-stream,\n
    \ but not the newly-pushed one. Now this causes a ``ProtocolError``.\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/www/py-h2'
  unixtime: '1461168614'
  user: leot