Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/hyper/http20/__pycache__/connection.cpython-36.opt-1.pyc |
FileSize | 23401 |
MD5 | 75F24C188919BD741054FD904AA8DB5F |
SHA-1 | 141BBCD08B58450674B98A0F525F6CB8C9CC48BD |
SHA-256 | A2F9AD20F1A4C4B48CB3A5F47E5177E78D2259C96F2FE9FEAA408A2083507086 |
SSDEEP | 384:pGXCnkbwJ12YBssEWgU9WLrFpupRH4wT71hLaZ333a6Vbu16:2AkUD1BsmU5p23T71AZbM16 |
TLSH | T1B9B219CA6A927637FE53F1B1211F47B0C235827B3361900138ACD5AE5F192A6F476ACD |
hashlookup:parent-total | 10 |
hashlookup:trust | 100 |
The searched file hash is included in 10 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 42F39BA07BD2AEBAE8563A94E748071B |
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 | python3-hyper |
PackageRelease | bp154.2.24 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 657F0801EDAC5862DA07555098E5B84BDEA55722 |
SHA-256 | EF35E0D1F6552F4115B17E06088BFF9F0A24D1850FACF1443FB5B6A161105E7D |
Key | Value |
---|---|
MD5 | 9D4AD520198778223752471D1E37E6F5 |
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.27.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | ECDB24866845BEBE21C6E1E585BEFAEFF1003A5C |
SHA-256 | BF9678254686331953BFF3357A988F714D3CEEDF6883328B11C97F4C0E37AB8E |
Key | Value |
---|---|
MD5 | EE227C7DB6CCFB83A4717384B284B3F6 |
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 | 10.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | DF53E4542DA9969B2ADF89F3AC75DC0E0C145D5F |
SHA-256 | DE48857F2551D3BDF84E7FBE9E8A1CC3C15A9FCF1E2A790E7BC45F2D34671531 |
Key | Value |
---|---|
MD5 | 02C7A569E651C657471F6DC2E4BAAC44 |
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 | lp153.26.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 39CE636C560E8B28412DA4AC69387B6B7BFA5A73 |
SHA-256 | A872B4E11497988E83C0B6906FB633CDAFF69A55B32880E73326720F776FFBDA |
Key | Value |
---|---|
MD5 | EA5F74A498C405E328F57E03E3416A65 |
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 | python3-hyper |
PackageRelease | bp155.3.12 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 519192E97C244E9AA457643EE9F61E8DECD8A764 |
SHA-256 | AFD33C75622B3EA52B4BB1C747A5EA8BCB19E99F8815D822C6E9B600065AAD34 |
Key | Value |
---|---|
MD5 | 3B9E488DE3D3F1B80E9AB1E34C300DF2 |
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.10.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | BB44EEC368D19B78EC30F4E694EBD62F3368A30B |
SHA-256 | CB85EB05AED3790E2DE5057AB3B0D3C9105BF50718E6CB0B816A2411D9580A19 |
Key | Value |
---|---|
MD5 | 0A819929CEF831E3E5806F6559B3033B |
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 | 26.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | D037002DB8CBD62C2CA720ECF5CDDDA8FEA3B715 |
SHA-256 | 70EEA4391538D7C971C5881AEC53436712041F9A262DD5A945A22EBCB4785F4B |
Key | Value |
---|---|
MD5 | 955F295D2D1E9A100D03E307A7CF5898 |
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 | python3-hyper |
PackageRelease | bp155.3.12 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | BD62EF194E71C1E7D8783E4435D72D0D4638F617 |
SHA-256 | 55B4425E9BD80186512A5E159331D564F2ECD19DF541C48D4E53F58CA0AF0A4F |
Key | Value |
---|---|
MD5 | 194D933E2B982F43B86F1AA970394E98 |
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 | 10.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | 3A1A33DF33A90CB5EF821BA5EF9EBA1A026E70C3 |
SHA-256 | EB1E4025DE7DBBBB29F1D5FAC0DEED778551A6823851E7E2AA0DEC22DA32AD6A |
Key | Value |
---|---|
MD5 | CFEF30CAE9A2A56439A5F203D1C266B8 |
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 | 26.1 |
PackageVersion | 0.7.0+git88.18b629b |
SHA-1 | AFF87E09D3D619E0E83C58DDE7773E34BFED424E |
SHA-256 | 8934E2E6903957C0B88C2DA3E2FA10757E00D16EECE27C5CB5BCCB110644DAC3 |