|
| 1 | +Metadata-Version: 1.1 |
| 2 | +Name: hyper |
| 3 | +Version: 0.0.1 |
| 4 | +Summary: HTTP/2.0 for Python |
| 5 | +Home-page: http://hyper.rtfd.org |
| 6 | +Author: Cory Benfield |
| 7 | + |
| 8 | +License: MIT License |
| 9 | +Description: ========================== |
| 10 | + Hyper: HTTP/2.0 for Python |
| 11 | + ========================== |
| 12 | + |
| 13 | + HTTP is changing under our feet. HTTP/1.1, our old friend, is being |
| 14 | + supplemented by the brand new HTTP/2.0 standard. HTTP/2.0 provides many |
| 15 | + benefits: improved speed, lower bandwidth usage, better connection management, |
| 16 | + and more. |
| 17 | + |
| 18 | + ``hyper`` provides these benefits to your Python code. How? Like this:: |
| 19 | + |
| 20 | + from hyper import HTTP20Connection |
| 21 | + |
| 22 | + conn = HTTP20Connection('twitter.com:443') |
| 23 | + conn.request('GET', '/') |
| 24 | + resp = conn.getresponse() |
| 25 | + |
| 26 | + print(resp.read()) |
| 27 | + |
| 28 | + Simple. |
| 29 | + |
| 30 | + Caveat Emptor! |
| 31 | + ============== |
| 32 | + |
| 33 | + Please be warned: ``hyper`` is in a very early alpha. You *will* encounter bugs |
| 34 | + when using it. In addition, there are very many rough edges. With that said, |
| 35 | + please try it out in your applications: I need your feedback to fix the bugs |
| 36 | + and file down the rough edges. |
| 37 | + |
| 38 | + Versions |
| 39 | + ======== |
| 40 | + |
| 41 | + ``hyper`` provides support for draft 9 of the HTTP/2.0 draft specification and |
| 42 | + draft 5 of the HPACK draft specification. As further drafts are released, |
| 43 | + ``hyper`` will be updated to support them. |
| 44 | + |
| 45 | + Compatibility |
| 46 | + ============= |
| 47 | + |
| 48 | + ``hyper`` is intended to be a drop-in replacement for ``http.client``, with a |
| 49 | + similar API. However, ``hyper`` intentionally does not name its classes the |
| 50 | + same way ``http.client`` does. This is because most servers do not support |
| 51 | + HTTP/2.0 at this time: I don't want you accidentally using ``hyper`` when you |
| 52 | + wanted ``http.client``. |
| 53 | + |
| 54 | + Contributing |
| 55 | + ============ |
| 56 | + |
| 57 | + ``hyper`` welcomes contributions from anyone! Unlike many other projects we are |
| 58 | + happy to accept cosmetic contributions and small contributions, in addition to |
| 59 | + large feature requests and changes. |
| 60 | + |
| 61 | + Before you contribute (either by opening an issue or filing a pull request), |
| 62 | + please read the following guidelines: |
| 63 | + |
| 64 | + 1. Check for issues, *both open and closed*, before raising a new one. It's |
| 65 | + possible your idea or problem has been discussed before. GitHub has a very |
| 66 | + useful search feature: I recommend using that for a few minutes. |
| 67 | + 2. Fork the repository on GitHub. |
| 68 | + 3. Run the tests to confirm that they all pass on your system. If they don't, |
| 69 | + you will need to investigate why they fail. ``hyper`` has a substantial |
| 70 | + suite of tests which should cover most failures. |
| 71 | + 4. Write tests that demonstrate your bug or feature. Ensure that they all fail. |
| 72 | + 5. Make your change. |
| 73 | + 6. Run the entire test suite again, confirming that all tests pass including |
| 74 | + the ones you just added. |
| 75 | + 7. Send a pull request. GitHub pull requests are the expected method of |
| 76 | + collaborating on this project. |
| 77 | + |
| 78 | + If for whatever reason you strongly object to the GitHub workflow, email the |
| 79 | + maintainer with a patch. |
| 80 | + |
| 81 | + License |
| 82 | + ======= |
| 83 | + |
| 84 | + ``hyper`` is made available under the MIT License. For more details, see the |
| 85 | + ``LICENSE`` file in the repository. |
| 86 | + |
| 87 | + Authors |
| 88 | + ======= |
| 89 | + |
| 90 | + ``hyper`` is maintained by Cory Benfield, with contributions from others. For |
| 91 | + more details about the contributors, please see ``CONTRIBUTORS.rst``. |
| 92 | + |
| 93 | +Platform: UNKNOWN |
| 94 | +Classifier: Development Status :: 3 - Alpha |
| 95 | +Classifier: Intended Audience :: Developers |
| 96 | +Classifier: License :: OSI Approved :: MIT License |
| 97 | +Classifier: Programming Language :: Python |
| 98 | +Classifier: Programming Language :: Python :: 3 |
| 99 | +Classifier: Programming Language :: Python :: 3.3 |
0 commit comments