Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/hyper/http11/connection.py |
FileSize | 16926 |
MD5 | A827A13D1D693B4FBD570FE38BF4A064 |
SHA-1 | 11E12D8B3FB3225DB60D6DD76F217C1D3B329B4B |
SHA-256 | B5C618C8506C7620E82105FF78A3A05AB8D0D90F53ADCBC14CBBFDE9BA9E2401 |
SSDEEP | 384:7pRv3tRyLhKn6iDNIEZvmlOcg+zh5APl6JtDLFt:XVahK6iDN1mTYPQDL3 |
TLSH | T19772C746CA62BE25C35BC814D8A3BA53B31F98072718547C3CBC825D6FA5595C1F2ECE |
hashlookup:parent-total | 11 |
hashlookup:trust | 100 |
The searched file hash is included in 11 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | F7D55F661ED629B5D9E6C9A561F0F1F5 |
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.22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | 695AAEBEDD88E3E68B50994682A0CA27E7FC19CB |
SHA-256 | C10F77CCB4A2AD7A9EF47B91734EC7D9B5854D3043FFE9971C57B672FB7642AC |
Key | Value |
---|---|
MD5 | 3F59D78B80A39A0036BA3FF94776E83E |
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 | python39-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | 42C1DEB35E755403F7D8C033355A4E47B548E0B7 |
SHA-256 | 88C505958550F94CCFB4B74245763458AC700E16FEC108083E2D5167E144137A |
Key | Value |
---|---|
MD5 | 9CA3A84844BA6CB920EEB0E3BC2FCC0C |
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 | python310-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | D5BF05AFDCFB182FBCAA9E63630E79CB80B9CBB6 |
SHA-256 | 70EE56AC121ED00425D8341EF94355C696DF65B629B2B4E74EDD7D1806A4F1B4 |
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 | FAA55CE2D8BC870702A9A605365AE8A0 |
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 | python38-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | 8FDD0E1C1F706FC846142382F2A508D7F43A2112 |
SHA-256 | 7CF1B25C61FC6FE13EA76911F2488569719E0004E0D08E03E5D4560B0DFF871D |
Key | Value |
---|---|
MD5 | 98F583E561CA193A88D941C9DE072870 |
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 | python39-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | D7D964093296ED4DCB16E05BCBA300C291CF24F5 |
SHA-256 | 1E439F9F43C8A35D189E90C4B85C51F534F019B25EE99CE5AA17C5BE3824966F |
Key | Value |
---|---|
MD5 | 3721DBB009D682D11321543A388FBA68 |
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 | python310-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | D0CE28693B655A6F347079CEAF94ED8227D5ACF1 |
SHA-256 | 06C28CCAE91D9A5E206CB3ECE02316FD64B5F04CD55965522950AC60E86D96F6 |
Key | Value |
---|---|
MD5 | 47B394AB78035FF011122B24169A977C |
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 | python38-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | F2E9C2E3E0BD5C66E1AC3E9EAE092F5F119AAEAB |
SHA-256 | 83B8E1E1927E69DE3F23A2B6FBA384084997B0570D4781977E68C93E7B660627 |
Key | Value |
---|---|
MD5 | DF7CC9D68A0AA662173AF5344AC0ADF3 |
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 | python310-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | FDDCA6E0F05E5C0C7F111D46E5D8C3D6566037CE |
SHA-256 | D40E5C4050925101A7BFD4242246C0B634196266C96FF57C0E0D7FA5F0F542B5 |
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 | C56FB860AEF75446FDA7ED1EF7DBC225 |
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 | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | B101C86102DB44498700B9DC18ED31DA6B7E4B90 |
SHA-256 | AB6B01131046F390252BA5FE565924747393C31F2C20DF3782D43D09764D0857 |