Result for 064957C93AB750DF757163B0FE81C88F753D915C

Query result

Key Value
FileName./usr/share/doc/packages/python3-hyper/README.rst
FileSize2777
MD584F6115CC4EA8744981B33A231925884
SHA-1064957C93AB750DF757163B0FE81C88F753D915C
SHA-256470733B09833A59767ED83D13892616FD5F4032EF403AC83AF203C434C88F550
SSDEEP48:7LWdLHN9/CmR4fbcuMapdtRPR87QVvS3L1CL+zMRinwImv2MKUH50wLK6:72bCn79pfR5g0vSpCqzA/IuxCs
TLSHT1DD5197C5BB1933F51BD30164B58AD1D2E728D15E27ADB22A4024D4B811DAB2EC13B79D
hashlookup:parent-total22
hashlookup:trust100

Network graph view

Parents (Total: 22)

The searched file hash is included in 22 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5E4BA4F1D0DD09EA1A15526EE30A553A7
PackageArcharmv7hl
PackageDescriptionhyper 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.
PackageNamepython39-hyper
PackageRelease22.1
PackageVersion0.7.0+git89.b77e758
SHA-105569304AD26B2DEEA49CCA3CFD35E0FC49BA849
SHA-25610F3F2267FC620A050973634339F280C0A19E4E16D66BEA60A336F4CF4B28336
Key Value
MD5230FA0E2EBD2DD933AD9CB6188644A32
PackageArchx86_64
PackageDescriptionhyper 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.
PackageNamepython3-hyper
PackageReleaselp154.3.1
PackageVersion0.7.0+git89.b77e758
SHA-10F5886BE598F899B92024B647F15D3F785202A26
SHA-256D3195C8328611CBF8840241B17530DD8D6A1C3CC4F1F1C0E87C728F29D505913
Key Value
MD561722E1FF1E5D3E60DA8FF9E09E533BF
PackageArchs390x
PackageDescriptionhyper 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.
PackageNamepython36-hyper
PackageRelease28.1
PackageVersion0.7.0+git89.b77e758
SHA-1279FA2FDDD2466B2B0A2547713982542C3D799AC
SHA-256DA6CB8EBA28C25C903DCD849483CFF33CAEFCDB3BAD431382D7433A1A105CF1E
Key Value
MD5C8EBDFBC52EAAF547EC0FA1991643305
PackageArchx86_64
PackageDescriptionhyper 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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython39-hyper
PackageRelease1.1
PackageVersion0.7.0+git89.b77e758
SHA-12E253CF65B1DE240AEEF6F5634F17AFFDE46DA6A
SHA-2566DE2A9A9B9A9CA3ABA87578125BC99D8665B1B028D2882BE697FB3C130DED483
Key Value
MD53F59D78B80A39A0036BA3FF94776E83E
PackageArchi586
PackageDescriptionhyper 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.
PackageNamepython39-hyper
PackageRelease22.1
PackageVersion0.7.0+git89.b77e758
SHA-142C1DEB35E755403F7D8C033355A4E47B548E0B7
SHA-25688C505958550F94CCFB4B74245763458AC700E16FEC108083E2D5167E144137A
Key Value
MD55D636B8CDD35E51857C5C5FDCA3E999B
PackageArchi586
PackageDescriptionhyper 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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython39-hyper
PackageRelease1.1
PackageVersion0.7.0+git89.b77e758
SHA-1540A74BC9B2B4D8E903C7958FC4D7E96B14C54C0
SHA-25639D89756AC6E872C76F8CD7A7BD401F61FD2FFA961A42A80BBC23F6C97517627
Key Value
MD5A8D8148E35DF7E832CA9B4FB2861CD7C
PackageArchs390x
PackageDescriptionhyper 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.
PackageNamepython39-hyper
PackageRelease28.1
PackageVersion0.7.0+git89.b77e758
SHA-15CCD1F0E0D433AF7752CDE40FB231010D1549067
SHA-2566F73C297F7C5052BD2B173088F7BD082653C40B9C79D19CD0C170CED2FB6FB15
Key Value
MD5E7E4BD6674281449063DA920EBDA59DE
PackageArchx86_64
PackageDescriptionhyper 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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython36-hyper
PackageRelease1.1
PackageVersion0.7.0+git89.b77e758
SHA-165C864D4FE66896297AABB849F550ED9A9AA43BB
SHA-2564E31AD3DE70BB6BC3F3F20F32F1D89A39A9CB141D9A3282E908CD181904C45CF
Key Value
MD5F7D55F661ED629B5D9E6C9A561F0F1F5
PackageArchx86_64
PackageDescriptionhyper 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.
PackageNamepython3-hyper
PackageReleaselp154.22.1
PackageVersion0.7.0+git89.b77e758
SHA-1695AAEBEDD88E3E68B50994682A0CA27E7FC19CB
SHA-256C10F77CCB4A2AD7A9EF47B91734EC7D9B5854D3043FFE9971C57B672FB7642AC
Key Value
MD5C3917324EA4331CE3D16B378919E712D
PackageArchs390x
PackageDescriptionhyper 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.
PackageNamepython38-hyper
PackageRelease28.1
PackageVersion0.7.0+git89.b77e758
SHA-17C1ED1D9A3D7DA1419C15DF165278009FE7C6792
SHA-2566B461FAF4E4548F8DF1D40E0C9003D20AFF82FCCB2597C6FCC41A55F28889C04