Key | Value |
---|---|
FileName | ./usr/lib/python2.7/site-packages/hyper/http11/parser.pyo |
FileSize | 2744 |
MD5 | 236EEFA3340EDE9426715CD320E66A99 |
SHA-1 | 1562CF7114F9F88B1FDC1FA4A63C4340C363016B |
SHA-256 | ED00FAF8FB893F8E0CD545CAB6902C12840848C79888629902B406F84C8BF1EF |
SSDEEP | 48:FJkWTlbdC8VgP1mhtq4U7vj3CGe42zsn8T10RgmVruW3TPm:nxdBVgP1mnq4G3SY8K2kuR |
TLSH | T13F512188BBE58503C2B21574E5A10907DF50D1B70386638075BCE1B96FE8265E83F388 |
hashlookup:parent-total | 17 |
hashlookup:trust | 100 |
The searched file hash is included in 17 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 | 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 | 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 | 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 |
Key | Value |
---|---|
MD5 | BA5EE713625780BC1952BBC5FEC64905 |
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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python2-hyper |
PackageRelease | bp153.1.17 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 514C04EC553FBA162201A6161250A84B8F70F5A0 |
SHA-256 | 33E801CE210E672D9FDC6087A1BE1BFD41D10CFD04B9CE757452B3F7FF0F6D25 |
Key | Value |
---|---|
MD5 | FF59881DD07EFDE7A06B513C338BC24F |
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 | 19.2 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 6E1C8F6AB630C71816E19C85CED80F57E34FA868 |
SHA-256 | F28F63DD5D20DD70311C7D15112F7F4DA9F29254D62DD59E331E577633DD2926 |
Key | Value |
---|---|
MD5 | BB7C8420DBD7A87B8ADFC489414D6FB4 |
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.9.3 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 72EFF960AB849ACB742ECEEEDD7958BB1AFB5554 |
SHA-256 | 385D9F38500FC33B182524D79A60BB9F2062F6796EF3FF401FCA092DA9D9A9BD |
Key | Value |
---|---|
MD5 | 86F3769B098DD2D843F3B6416AAC0A6D |
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 | lp150.4.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | A7C51535642BE5001B4720BD62B05F384FB28380 |
SHA-256 | A634E4E114C29759A50F0508CC86DFFC6869E02A7F69A5805CA7035DCD5A9015 |