Result for 119DA29533387E649651C3D14A0E85B466E754A9

Query result

Key Value
FileName./usr/lib/python3.9/site-packages/hyper/__pycache__/cli.cpython-39.opt-1.pyc
FileSize6977
MD5D1638BD6A2F16A52FD1EBCC58CFCE42E
SHA-1119DA29533387E649651C3D14A0E85B466E754A9
SHA-256BE6BDADF80393CFB8BB8A49331DB2714E3BC423244D7203DB118E77F83F09DA7
SSDEEP96:EaO50BtoxMc/qElrynQIid2VNpwmdt0Jrvez0Xhaqezu5Hc4160Rc16ByfeIYAmX:h8QtoxzdIn36PpeAXh6zuV8vCAnrBm
TLSHT11EE1C6C649415A9BFD27F3BE541A4A50A720A36FB34DB81BB41C02AE1F8E5D60D3268D
tar:gnameroot
tar:unameroot
hashlookup:parent-total8
hashlookup:trust90

Network graph view

Parents (Total: 8)

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
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
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
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
MD5C6DB909AB7C0042B756D98DD39E4ED3C
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
PackageRelease27.2
PackageVersion0.7.0+git88.18b629b
SHA-113F6EB6D27DB5630D67FB0588BA8BB282B682335
SHA-2563240E5DC01A1D984214FC7E1FF5B1A508D3D7ED6FC62F3F4D06CFD7C3CB14745
Key Value
MD598F583E561CA193A88D941C9DE072870
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.
PackageNamepython39-hyper
PackageRelease22.1
PackageVersion0.7.0+git89.b77e758
SHA-1D7D964093296ED4DCB16E05BCBA300C291CF24F5
SHA-2561E439F9F43C8A35D189E90C4B85C51F534F019B25EE99CE5AA17C5BE3824966F
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
FileNamehttp://mirror.math.princeton.edu/pub/blackarch/blackarch/os//x86_64//python-hyper-0.7.0-4-any.pkg.tar.zst
MD524E9EBD01D0D28CD4AA2B09DCB2F6B81
SHA-1A896752C4EE78C7D075D946F3586749A7B8D1B65
SHA-2565B4EE09D262F8B1E42EE3B547424E89ADFAF8BB106BE3CF3C8C18F4038ABB651
SSDEEP6144:OmfJCqZnpAuVWh5gIPJozcP96ofII09C9rl:hpA15leIPe9m
TLSHT14C44236FCCBE63A431C6E14373E49AC06BAA474EC27110136D1B74F9B05359E819DE9E
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