| Key | Value |
|---|---|
| FileName | ./usr/lib/python3.6/site-packages/hyper-0.8.0.dev0-py3.6.egg-info/requires.txt |
| FileSize | 329 |
| MD5 | F17BE48DB990A90C249745740D746BD8 |
| SHA-1 | 09A178E65E7A45F69640401D02D30476CF9856BF |
| SHA-256 | BAEB2748799D4996B98B687787F3736F2B5D1CF9D72AD371A8419D60938A04BF |
| SSDEEP | 6:6RQV8IEHcqOAFd/EOPPy7H2LfhVBZ40y7H2LfMiix4Ofq0X8jz5X8OxHv0GkDzVC:6A8IcJ1FdxeWt940eWojq0Ez5vxHv0/Q |
| TLSH | T1A2E07DDA5E64DCF56C27014CD0AB062AC71110853A4C211CE23191D53EB22F9C2F038B |
| hashlookup:parent-total | 54 |
| hashlookup:trust | 100 |
The searched file hash is included in 54 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | E4BA4F1D0DD09EA1A15526EE30A553A7 |
| PackageArch | armv7hl |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python39-hyper |
| PackageRelease | 22.1 |
| PackageVersion | 0.7.0+git89.b77e758 |
| SHA-1 | 05569304AD26B2DEEA49CCA3CFD35E0FC49BA849 |
| SHA-256 | 10F3F2267FC620A050973634339F280C0A19E4E16D66BEA60A336F4CF4B28336 |
| Key | Value |
|---|---|
| MD5 | 230FA0E2EBD2DD933AD9CB6188644A32 |
| PackageArch | x86_64 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python3-hyper |
| PackageRelease | lp154.3.1 |
| PackageVersion | 0.7.0+git89.b77e758 |
| SHA-1 | 0F5886BE598F899B92024B647F15D3F785202A26 |
| SHA-256 | D3195C8328611CBF8840241B17530DD8D6A1C3CC4F1F1C0E87C728F29D505913 |
| Key | Value |
|---|---|
| MD5 | 31955200C08CDF52593FF20218F74FCF |
| PackageArch | x86_64 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python2-hyper |
| PackageRelease | lp153.26.1 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 10F0E361EB08A214FDC727B05299B9570B8B0BA8 |
| SHA-256 | F8546291C6BC86AE48824B6D0E75FA5298FEC99A585A869B1A60FCD83928AD7D |
| Key | Value |
|---|---|
| MD5 | D6A363DDF2582209474BEB9C1B9ADFBF |
| PackageArch | x86_64 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python2-hyper |
| PackageRelease | 10.1 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 11EBF0E259AE64C5A461D4ADD0523A9862DFA19F |
| SHA-256 | 078BACBBDF15CCFC8606F52383C8FC6110F82EEB8C8A5965116A261E01DAC578 |
| Key | Value |
|---|---|
| MD5 | C6DB909AB7C0042B756D98DD39E4ED3C |
| PackageArch | armv7hl |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python39-hyper |
| PackageRelease | 27.2 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 13F6EB6D27DB5630D67FB0588BA8BB282B682335 |
| SHA-256 | 3240E5DC01A1D984214FC7E1FF5B1A508D3D7ED6FC62F3F4D06CFD7C3CB14745 |
| Key | Value |
|---|---|
| MD5 | CE588096A5AEFD7C1CE008D4DC3E730E |
| PackageArch | x86_64 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python3-hyper |
| PackageRelease | 7.2 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 14A5A787E85C373FC4467C0EE55D6D1CED38DBB9 |
| SHA-256 | 9B828B0CB09B33F0E41ED8E8BC27A3959DD89A5092CF054EA4B85163104E67F6 |
| Key | Value |
|---|---|
| MD5 | 0FF21B8F566A9CFA821D1CEB097DD66A |
| PackageArch | x86_64 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python3-hyper |
| PackageRelease | 19.2 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 15754C062B825746514E015887B8067EA29655F0 |
| SHA-256 | 6677A4EC3B010F11AD333EE4D5EB9A83E0C61C2BB822E4C256DD110FD105C88F |
| Key | Value |
|---|---|
| MD5 | D65F069CF43D2DA4587DD88381293A40 |
| PackageArch | armv7hl |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python38-hyper |
| PackageRelease | 27.2 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 170E5BC1F3AEB893E706FB7611C7C4AA977ED25B |
| SHA-256 | B7636DF11E69A857937F28740F7367B26E09B8F083430F63781B8C5CBB9308FB |
| Key | Value |
|---|---|
| MD5 | 61722E1FF1E5D3E60DA8FF9E09E533BF |
| PackageArch | s390x |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python36-hyper |
| PackageRelease | 28.1 |
| PackageVersion | 0.7.0+git89.b77e758 |
| SHA-1 | 279FA2FDDD2466B2B0A2547713982542C3D799AC |
| SHA-256 | DA6CB8EBA28C25C903DCD849483CFF33CAEFCDB3BAD431382D7433A1A105CF1E |
| Key | Value |
|---|---|
| MD5 | C8EBDFBC52EAAF547EC0FA1991643305 |
| PackageArch | x86_64 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | python39-hyper |
| PackageRelease | 1.1 |
| PackageVersion | 0.7.0+git89.b77e758 |
| SHA-1 | 2E253CF65B1DE240AEEF6F5634F17AFFDE46DA6A |
| SHA-256 | 6DE2A9A9B9A9CA3ABA87578125BC99D8665B1B028D2882BE697FB3C130DED483 |