Result for 0AF3FE9259EBF007838D6AC07CA1381E8C36DFE1

Query result

Key Value
FileName./usr/lib/python3.8/site-packages/hyper/http20/__pycache__/stream.cpython-38.pyc
FileSize9487
MD5F07BA7BDED8B696037DECA63E294A320
SHA-10AF3FE9259EBF007838D6AC07CA1381E8C36DFE1
SHA-256AC0CA1D75394A95A3756FDD456650DF7716AC87400E47C744A8B31796C712F5E
SSDEEP192:lFw35rvdMgitS4dhAUfbGvCUBswGZhPENmq/a/q/aOBcq2mAoPdJlrG:lqZFMZpd+kGvPBKxE2/bEcnmA8dJlrG
TLSHT16212A58B7D412B1BFF11F1B4A84A7350B360A277672990533A2CE46E2FC9694B5317CC
hashlookup:parent-total9
hashlookup:trust95

Network graph view

Parents (Total: 9)

The searched file hash is included in 9 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
MD54D4CE62F49D0E4464C04B82D76FF4C3E
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
PackageNamepython38-hyper
PackageRelease1.1
PackageVersion0.7.0+git89.b77e758
SHA-1D2F38FB39E174CF806F4E9C039284802078EE1E3
SHA-256457F76CE42FD45280CC39768D5665F0798629124D089D0ED0243A4459A48DAFF
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
MD5FAA55CE2D8BC870702A9A605365AE8A0
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.
PackageNamepython38-hyper
PackageRelease22.1
PackageVersion0.7.0+git89.b77e758
SHA-18FDD0E1C1F706FC846142382F2A508D7F43A2112
SHA-2567CF1B25C61FC6FE13EA76911F2488569719E0004E0D08E03E5D4560B0DFF871D
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
MD590B6C13527ED658F186955D3090003D1
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.
PackageNamepython3-hyper
PackageRelease5.4
PackageVersion0.7.0+git88.18b629b
SHA-133350A3F029B1B4232ED956213916893674A6D97
SHA-256BAC62FD10BB43D329B2AB972DFA0700260374DEA5C44B7823766CE8C73D83617
Key Value
MD5D65F069CF43D2DA4587DD88381293A40
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.
PackageNamepython38-hyper
PackageRelease27.2
PackageVersion0.7.0+git88.18b629b
SHA-1170E5BC1F3AEB893E706FB7611C7C4AA977ED25B
SHA-256B7636DF11E69A857937F28740F7367B26E09B8F083430F63781B8C5CBB9308FB
Key Value
MD5C56FB860AEF75446FDA7ED1EF7DBC225
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.
PackageNamepython38-hyper
PackageRelease22.1
PackageVersion0.7.0+git89.b77e758
SHA-1B101C86102DB44498700B9DC18ED31DA6B7E4B90
SHA-256AB6B01131046F390252BA5FE565924747393C31F2C20DF3782D43D09764D0857
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