python-hyperframe 3.2.0-2 / usr / lib / python2.7 / dist-packages / hyperframe-3.2.0.egg-info / PKG-INFO

This file is indexed.

/usr/lib/python2.7/dist-packages/hyperframe-3.2.0.egg-info/PKG-INFO is in python-hyperframe 3.2.0-2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
Metadata-Version: 1.1
Name: hyperframe
Version: 3.2.0
Summary: HTTP/2 framing layer for Python
Home-page: http://hyper.rtfd.org
Author: Cory Benfield
Author-email: cory@lukasa.co.uk
License: MIT License
Description: ======================================
        hyperframe: Pure-Python HTTP/2 framing
        ======================================
        
        .. image:: https://travis-ci.org/python-hyper/hyperframe.png?branch=master
            :target: https://travis-ci.org/python-hyper/hyperframe
        
        This library contains the HTTP/2 framing code used in the `hyper`_ project. It
        provides a pure-Python codebase that is capable of decoding a binary stream
        into HTTP/2 frames.
        
        This library is used directly by `hyper`_ and a number of other projects to
        provide HTTP/2 frame decoding logic.
        
        Contributing
        ============
        
        hyperframe welcomes contributions from anyone! Unlike many other projects we
        are happy to accept cosmetic contributions and small contributions, in addition
        to large feature requests and changes.
        
        Before you contribute (either by opening an issue or filing a pull request),
        please `read the contribution guidelines`_.
        
        .. _read the contribution guidelines: http://hyper.readthedocs.org/en/development/contributing.html
        
        License
        =======
        
        hyperframe is made available under the MIT License. For more details, see the
        ``LICENSE`` file in the repository.
        
        Authors
        =======
        
        hyperframe is maintained by Cory Benfield, with contributions from others. For
        more details about the contributors, please see ``CONTRIBUTORS.rst``.
        
        .. _hyper: http://python-hyper.org/
        
        
        Release History
        ===============
        
        dev
        ---
        
        **API Changes (Backward-compatible)**
        
        - Invalid PING frame bodies now raise ``InvalidFrameError``, not
          ``ValueError``. Note that ``InvalidFrameError`` is a ``ValueError`` subclass.
        - Invalid RST_STREAM frame bodies now raise ``InvalidFramError``, not
          ``ValueError``. Note that ``InvalidFrameError`` is a ``ValueError`` subclass.
        - Canonicalized the names of ``SettingsFrame.SETTINGS_MAX_FRAME_SIZE`` and
          ``SettingsFrame.SETTINGS_MAX_HEADER_LIST_SIZE`` to match their peers, by
          adding new properties ``SettingsFrame.MAX_FRAME_SIZE`` and
          ``SettingsFrame.SETTINGS_MAX_HEADER_LIST_SIZE``. The old names are still
          present, but will be deprecated in 4.0.0.
        
        **Bugfixes**
        
        - The change in ``3.1.0`` that ensured that ``InvalidFrameError`` would be
          thrown did not affect certain invalid values in ALT_SVC frames. This has been
          fixed: ``ValueError`` will no longer be thrown from invalid ALT_SVC bodies.
        
        3.1.1 (2016-01-18)
        ------------------
        
        **Bugfixes**
        
        - Correctly error when receiving Ping frames that have insufficient data.
        
        3.1.0 (2016-01-13)
        ------------------
        
        **API Changes**
        
        - Added new ``InvalidFrameError`` that is thrown instead of ``struct.error``
          when parsing a frame.
        
        **Bugfixes**
        
        - Fixed error when trying to serialize frames that use Priority information
          with the defaults for that information.
        - Fixed errors when displaying the repr of frames with non-printable bodies.
        
        3.0.1 (2016-01-08)
        ------------------
        
        **Bugfixes**
        
        - Fix issue where unpadded DATA, PUSH_PROMISE and HEADERS frames that had empty
          bodies would raise ``InvalidPaddingError`` exceptions when parsed.
        
        3.0.0 (2016-01-08)
        ------------------
        
        **Backwards Incompatible API Changes**
        
        - Parsing padded frames that have invalid padding sizes now throws an
          ``InvalidPaddingError``.
        
        2.2.0 (2015-10-15)
        ------------------
        
        **API Changes**
        
        - When an unknown frame is encountered, ``parse_frame_header`` now throws a
          ``ValueError`` subclass: ``UnknownFrameError``. This subclass contains the
          frame type and the length of the frame body.
        
        2.1.0 (2015-10-06)
        ------------------
        
        **API Changes**
        
        - Frames parsed from binary data now carry a ``body_len`` attribute that
          matches the frame length (minus the frame header).
        
        2.0.0 (2015-09-21)
        ------------------
        
        **API Changes**
        
        - Attempting to parse unrecognised frames now throws ``ValueError`` instead of
          ``KeyError``.  Thanks to @Kriechi!
        - Flags are now validated for correctness, preventing setting flags that
          ``hyperframe`` does not recognise and that would not serialize. Thanks to
          @mhils!
        - Frame properties can now be initialized in the constructors. Thanks to @mhils
          and @Kriechi!
        - Frames that cannot be sent on a stream now have their stream ID defaulted
          to ``0``. Thanks to @Kriechi!
        
        **Other Changes**
        
        - Frames have a more useful repr. Thanks to @mhils!
        
        1.1.1 (2015-07-20)
        ------------------
        
        - Fix a bug where ``FRAME_MAX_LEN`` was one byte too small.
        
        1.1.0 (2015-06-28)
        ------------------
        
        - Add ``body_len`` property to frames to enable introspection of the actual
          frame length. Thanks to @jdecuyper!
        
        1.0.1 (2015-06-27)
        ------------------
        
        - Fix bug where the frame header would have an incorrect length added to it.
        
        1.0.0 (2015-04-12)
        ------------------
        
        - Initial extraction from `hyper`_.
        
        .. _hyper: http://hyper.readthedocs.org/
        
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: Implementation :: CPython

APT Browse - Built by Thomas Orozco.