Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/hyper-0.8.0.dev0-py3.6.egg-info/PKG-INFO |
FileSize | 18636 |
MD5 | 95CC3B43697B34E4B13273D75C81BA15 |
SHA-1 | 00A5FB60F70252C2AA550CED4BEEB375AB9430F6 |
SHA-256 | 272FA380F45BA250FB90613C1FD2CBCD44938C22E2851417DF8267FFD9FAE968 |
SSDEEP | 384:TnkpeZQuNqj/XOv+d5DFU4JhdC3r+VAtCIv:T2uNMvju6dW+Ne |
TLSH | T15882A54F3E0835A01F93C4B2A5C54562E731909BE7D8B859B0EF806D4F59B25CB7F298 |
hashlookup:parent-total | 31 |
hashlookup:trust | 100 |
The searched file hash is included in 31 parent files which include package known and seen by metalookup. A sample is included below:
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 | 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 | 2D0225AA8B060518D62B553576D1D9EC |
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 | python2-hyper |
PackageRelease | bp153.1.17 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 15B2457D1DBF96D0ED360C83D507C82D7260EDAB |
SHA-256 | 28A3010B889C02A09236690D2CC739E35416F53444512A06602E09E9DEE211EF |
Key | Value |
---|---|
MD5 | FD977E82A0AFC1EFF47BA6B0EF740056 |
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 | lp150.4.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 28352AF5E5F7052077A53727234C7E1D74F7028F |
SHA-256 | CF24617F83F764AD290F367316C476FEA5FB6C96A4817CA6E127C143593BE7AB |
Key | Value |
---|---|
MD5 | DE6E13B8FD78A188C4548D5312FE62E2 |
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 | 26.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 3230F2266BE15644579CB1137DCF75D4D24C09B0 |
SHA-256 | CF3248F47573386ED176808A402EFC9CF51ACB5CF42094DC6D5AF1F255082508 |
Key | Value |
---|---|
MD5 | 90B6C13527ED658F186955D3090003D1 |
PackageArch | i586 |
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 | 5.4 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 33350A3F029B1B4232ED956213916893674A6D97 |
SHA-256 | BAC62FD10BB43D329B2AB972DFA0700260374DEA5C44B7823766CE8C73D83617 |
Key | Value |
---|---|
MD5 | ECABFF93DFCDDFDF289C6A665DC06610 |
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 | lp151.19.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 3B93F9614955E2B4AD7A1F36330081EB8F571C86 |
SHA-256 | C503B2737920AA89E6F7216D297DE9C1CFAA234A9A6A404C76FD1CFCB5A83D1F |
Key | Value |
---|---|
MD5 | 6B8291A1778D46FD60D38137D29D8883 |
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 | 26.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 4DD7441833790829FB35FA60C17634BB1B2B9FAD |
SHA-256 | 1EB6A883CF93DCCD48831CA762B55A10512EFCF70359CD8531885157DE4632F3 |