Result for 0BAF7A021A908B03D5EF5822632761193C5659B3

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/hyper/__init__.pyo
FileSize1107
MD57F075D212F35215FC0C2144BDC2076B8
SHA-10BAF7A021A908B03D5EF5822632761193C5659B3
SHA-25691C1E795D90A12AF81696ADA90F19E638975934BB8F22DA2D1944A1882C09F6B
SSDEEP24:axzIIzoWIVqkYVSUAUN9PyXOybBzjxraR/ca1MsEpQoVZelMswPF:ezFzofb+RAU3PyXOybBJ2R/XEwlZ0F
TLSHT16111128677CE5F93F39F4234809A0213A570B4B35705D7421778B0604EF236264366DF
hashlookup:parent-total17
hashlookup:trust100

Network graph view

Parents (Total: 17)

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

Key Value
MD531955200C08CDF52593FF20218F74FCF
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.
PackageNamepython2-hyper
PackageReleaselp153.26.1
PackageVersion0.7.0+git88.18b629b
SHA-110F0E361EB08A214FDC727B05299B9570B8B0BA8
SHA-256F8546291C6BC86AE48824B6D0E75FA5298FEC99A585A869B1A60FCD83928AD7D
Key Value
MD5D6A363DDF2582209474BEB9C1B9ADFBF
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.
PackageNamepython2-hyper
PackageRelease10.1
PackageVersion0.7.0+git88.18b629b
SHA-111EBF0E259AE64C5A461D4ADD0523A9862DFA19F
SHA-256078BACBBDF15CCFC8606F52383C8FC6110F82EEB8C8A5965116A261E01DAC578
Key Value
MD52D0225AA8B060518D62B553576D1D9EC
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
PackageNamepython2-hyper
PackageReleasebp153.1.17
PackageVersion0.7.0+git88.18b629b
SHA-115B2457D1DBF96D0ED360C83D507C82D7260EDAB
SHA-25628A3010B889C02A09236690D2CC739E35416F53444512A06602E09E9DEE211EF
Key Value
MD5DE6E13B8FD78A188C4548D5312FE62E2
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.
PackageNamepython2-hyper
PackageRelease26.1
PackageVersion0.7.0+git88.18b629b
SHA-13230F2266BE15644579CB1137DCF75D4D24C09B0
SHA-256CF3248F47573386ED176808A402EFC9CF51ACB5CF42094DC6D5AF1F255082508
Key Value
MD5ECABFF93DFCDDFDF289C6A665DC06610
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.
PackageNamepython2-hyper
PackageReleaselp151.19.1
PackageVersion0.7.0+git88.18b629b
SHA-13B93F9614955E2B4AD7A1F36330081EB8F571C86
SHA-256C503B2737920AA89E6F7216D297DE9C1CFAA234A9A6A404C76FD1CFCB5A83D1F
Key Value
MD56B8291A1778D46FD60D38137D29D8883
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.
PackageNamepython2-hyper
PackageRelease26.1
PackageVersion0.7.0+git88.18b629b
SHA-14DD7441833790829FB35FA60C17634BB1B2B9FAD
SHA-2561EB6A883CF93DCCD48831CA762B55A10512EFCF70359CD8531885157DE4632F3
Key Value
MD5BA5EE713625780BC1952BBC5FEC64905
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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython2-hyper
PackageReleasebp153.1.17
PackageVersion0.7.0+git88.18b629b
SHA-1514C04EC553FBA162201A6161250A84B8F70F5A0
SHA-25633E801CE210E672D9FDC6087A1BE1BFD41D10CFD04B9CE757452B3F7FF0F6D25
Key Value
MD5FF59881DD07EFDE7A06B513C338BC24F
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.
PackageNamepython2-hyper
PackageRelease19.2
PackageVersion0.7.0+git88.18b629b
SHA-16E1C8F6AB630C71816E19C85CED80F57E34FA868
SHA-256F28F63DD5D20DD70311C7D15112F7F4DA9F29254D62DD59E331E577633DD2926
Key Value
MD5BB7C8420DBD7A87B8ADFC489414D6FB4
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.
PackageNamepython2-hyper
PackageReleaselp153.9.3
PackageVersion0.7.0+git88.18b629b
SHA-172EFF960AB849ACB742ECEEEDD7958BB1AFB5554
SHA-256385D9F38500FC33B182524D79A60BB9F2062F6796EF3FF401FCA092DA9D9A9BD
Key Value
MD586F3769B098DD2D843F3B6416AAC0A6D
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.
PackageNamepython2-hyper
PackageReleaselp150.4.1
PackageVersion0.7.0+git88.18b629b
SHA-1A7C51535642BE5001B4720BD62B05F384FB28380
SHA-256A634E4E114C29759A50F0508CC86DFFC6869E02A7F69A5805CA7035DCD5A9015