Key | Value |
---|---|
FileName | ./usr/lib/python3.9/site-packages/hyper/http20/__pycache__/errors.cpython-39.opt-1.pyc |
FileSize | 1953 |
MD5 | 554F09531327A804A0E0E207AE693A09 |
SHA-1 | 1664596ABAFF18D4CB3438701EA6E792D760DD32 |
SHA-256 | 0FEE5CD1B7E3FB31C2BEF92D639FF0723302BC4DB0848BBF7E529568F2C15BC6 |
SSDEEP | 48:s+QHntfY6nyAcAvgk1ADzURgz53XoDfXbbWZfwtqfmqqqqqqqqqkB:sPHS6HgQAXpXCCoMfm |
TLSH | T10C41EB4F2E3B17B7FADAB1B26016423197F80352571AB168495B47085E757F09C71B0C |
tar:gname | root |
tar:uname | root |
hashlookup:parent-total | 8 |
hashlookup:trust | 90 |
The searched file hash is included in 8 parent files which include package known and seen by metalookup. A sample is included below:
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 | 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 |
Key | Value |
---|---|
MD5 | 5D636B8CDD35E51857C5C5FDCA3E999B |
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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python39-hyper |
PackageRelease | 1.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | 540A74BC9B2B4D8E903C7958FC4D7E96B14C54C0 |
SHA-256 | 39D89756AC6E872C76F8CD7A7BD401F61FD2FFA961A42A80BBC23F6C97517627 |
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 | 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 | 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 |
---|---|
FileName | http://mirror.math.princeton.edu/pub/blackarch/blackarch/os//x86_64//python-hyper-0.7.0-4-any.pkg.tar.zst |
MD5 | 24E9EBD01D0D28CD4AA2B09DCB2F6B81 |
SHA-1 | A896752C4EE78C7D075D946F3586749A7B8D1B65 |
SHA-256 | 5B4EE09D262F8B1E42EE3B547424E89ADFAF8BB106BE3CF3C8C18F4038ABB651 |
SSDEEP | 6144:OmfJCqZnpAuVWh5gIPJozcP96ofII09C9rl:hpA15leIPe9m |
TLSH | T14C44236FCCBE63A431C6E14373E49AC06BAA474EC27110136D1B74F9B05359E819DE9E |
Key | Value |
---|---|
MD5 | A8D8148E35DF7E832CA9B4FB2861CD7C |
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 | python39-hyper |
PackageRelease | 28.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | 5CCD1F0E0D433AF7752CDE40FB231010D1549067 |
SHA-256 | 6F73C297F7C5052BD2B173088F7BD082653C40B9C79D19CD0C170CED2FB6FB15 |