Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/hyper/http20/__pycache__/connection.cpython-36.opt-1.pyc |
FileSize | 23401 |
MD5 | 1667BA5A9966AD6798A08D09CE24D3E3 |
SHA-1 | 0061DF184D7EEC018C2D427D3D6E4E4E59136EAD |
SHA-256 | 157745183D752321DA437DA92CA3C26EC2EEDB23BF72934552A26C0C2E70B60D |
SSDEEP | 384:wGXCnkbwJ12YBssEWgU9WLrFpupRH4wT71hLaZ333a6Vbu16:NAkUD1BsmU5p23T71AZbM16 |
TLSH | T1E5B219CA6A927637FE53F1B1211F47B0C235827B3361900138ACD5AE5F192A6F476ACD |
hashlookup:parent-total | 3 |
hashlookup:trust | 65 |
The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | E7E4BD6674281449063DA920EBDA59DE |
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 | python36-hyper |
PackageRelease | 1.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | 65C864D4FE66896297AABB849F550ED9A9AA43BB |
SHA-256 | 4E31AD3DE70BB6BC3F3F20F32F1D89A39A9CB141D9A3282E908CD181904C45CF |
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 | 37C052973B7E3BE5027F6C90648E8563 |
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 | python36-hyper |
PackageRelease | 1.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | EE2CA77A5E4157ECEEAF8D6F0BFF56E12C3BA61E |
SHA-256 | DC36E04120F713851032C66AA088F9ABF57A1ACA6F7863668A4C0DBA24F178CA |