Result for 04BBBF3FF7EEB24B4368A7BF6C5D762EF3CFB4DF

Query result

Key Value
FileName./usr/lib/python3.8/site-packages/hyper/__pycache__/cli.cpython-38.opt-1.pyc
FileSize7001
MD58FE39A0E7DD833343C283F1F60EB34C7
SHA-104BBBF3FF7EEB24B4368A7BF6C5D762EF3CFB4DF
SHA-25672024310D631FFA36173BA93037D25654217A2BB8650F0C78BFE5753CA0B4993
SSDEEP96:DaO50BtoQMc/qElrynQIid2VNpwmdt0JnezZXhaqezu5Rc4160Rc16jyfKZYDOeJ:+8QtoQzdIn36PNe1Xh6zuD8vLDlYnm
TLSHT10FE1C7C649405A9BFE77F3BE541A4A50A330A37F734DA85BB04C12AE1F8E6D60D3264C
hashlookup:parent-total4
hashlookup:trust70

Network graph view

Parents (Total: 4)

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

Key Value
MD50194DCC0D0138FDAF7BB9A0AADCE2BCF
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
PackageRelease5.4
PackageVersion0.7.0+git88.18b629b
SHA-1EE2B4B530D63A98FFA824EDF4F19B6F168C45D27
SHA-25695FE73F3732D0B9D3902B9C5DD1A8AB905B74BDCA6605511EA39A7D437F6CC5B
Key Value
MD547B394AB78035FF011122B24169A977C
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.
PackageNamepython38-hyper
PackageRelease22.1
PackageVersion0.7.0+git89.b77e758
SHA-1F2E9C2E3E0BD5C66E1AC3E9EAE092F5F119AAEAB
SHA-25683B8E1E1927E69DE3F23A2B6FBA384084997B0570D4781977E68C93E7B660627
Key Value
MD57C56FBED49628DCC37FF40576691CFF2
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
PackageNamepython38-hyper
PackageRelease1.1
PackageVersion0.7.0+git89.b77e758
SHA-1D7DFD36DB1559AD9E968BFA6A14DB5FBA42AE8AC
SHA-25648AAB58271EC30A4C01446F72386FBE413DA4EFC51C783309204E7DCF943B854
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