Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/hyper/http20/__pycache__/stream.cpython-36.pyc |
FileSize | 9439 |
MD5 | DB92274B7D8909842E063A1B6E1E7F1D |
SHA-1 | 07249DB1E4F3923DB8D110AE6E4B4DEE34FE6DDF |
SHA-256 | 523FDAD5CF0E0EE6379C74D9DDCD44D95DE475C2DBE2C863E295C3EC6F28C50B |
SSDEEP | 192:MFw35LvdcgirNAvAhzXH7WvdaRQtwGZEiKnQ/a/vD/aOBHfsqJJ5jED:MqZFcfWvAhrWvQ0z8/veEkqJ7jED |
TLSH | T1DA12948B3D812B1BFF12F2B4A44A73507360A27763699053392CE45E6FC6694B931BDC |
hashlookup:parent-total | 7 |
hashlookup:trust | 85 |
The searched file hash is included in 7 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 | F4F60FA2AF5BB7748130DADB64D62670 |
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 | lp152.2.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | FFF4B68E4B3D5F6A22FD57EB1FFF1518CCF158A9 |
SHA-256 | 03FA9C2DD7B8F2295E0D505C0C34438B033A0A11967FE265F5DF37B8BDCD48F9 |
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 | 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 | 9A19C725D1BD970FF7AD8D24E2BD9B4D |
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 | 2.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | D3755EF8107255BE2D90D9F9E0D96056F7E1164E |
SHA-256 | A0379C038A6B4AC449449BCDD9DA4F33D453643881F770091990D3065E8CC0B8 |
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 |