Parents (Total: 21)

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

Key	Value
MD5	CE588096A5AEFD7C1CE008D4DC3E730E
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	7.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	14A5A787E85C373FC4467C0EE55D6D1CED38DBB9
SHA-256	9B828B0CB09B33F0E41ED8E8BC27A3959DD89A5092CF054EA4B85163104E67F6

Key	Value
MD5	0FF21B8F566A9CFA821D1CEB097DD66A
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	19.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	15754C062B825746514E015887B8067EA29655F0
SHA-256	6677A4EC3B010F11AD333EE4D5EB9A83E0C61C2BB822E4C256DD110FD105C88F

Key	Value
MD5	FD977E82A0AFC1EFF47BA6B0EF740056
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	lp150.4.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	28352AF5E5F7052077A53727234C7E1D74F7028F
SHA-256	CF24617F83F764AD290F367316C476FEA5FB6C96A4817CA6E127C143593BE7AB

Key	Value
MD5	02C7A569E651C657471F6DC2E4BAAC44
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	lp153.26.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	39CE636C560E8B28412DA4AC69387B6B7BFA5A73
SHA-256	A872B4E11497988E83C0B6906FB633CDAFF69A55B32880E73326720F776FFBDA

Key	Value
MD5	194D933E2B982F43B86F1AA970394E98
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	10.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	3A1A33DF33A90CB5EF821BA5EF9EBA1A026E70C3
SHA-256	EB1E4025DE7DBBBB29F1D5FAC0DEED778551A6823851E7E2AA0DEC22DA32AD6A

Key	Value
MD5	EA5F74A498C405E328F57E03E3416A65
PackageArch	x86_64
PackageDescription	hyper 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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-hyper
PackageRelease	bp155.3.12
PackageVersion	0.7.0+git88.18b629b
SHA-1	519192E97C244E9AA457643EE9F61E8DECD8A764
SHA-256	AFD33C75622B3EA52B4BB1C747A5EA8BCB19E99F8815D822C6E9B600065AAD34

Key	Value
MD5	3A4F2A7B5A1BC12914DE797EDC133622
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	lp151.19.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	5A91E4A8BFCEDAAFF82AC612E2A665931571EEE0
SHA-256	EB5AD2059B7211FD22186A03BEC1B1236698F5E9C39C38F7F82BDC1A4A6C5469

Key	Value
MD5	42F39BA07BD2AEBAE8563A94E748071B
PackageArch	x86_64
PackageDescription	hyper 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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-hyper
PackageRelease	bp154.2.24
PackageVersion	0.7.0+git88.18b629b
SHA-1	657F0801EDAC5862DA07555098E5B84BDEA55722
SHA-256	EF35E0D1F6552F4115B17E06088BFF9F0A24D1850FACF1443FB5B6A161105E7D

Key	Value
MD5	2AF32E8E1CF06955D1A1DE7E08A528A2
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	4.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	89E4611258A6AA28FC565B47CCE9734AD59FCAE7
SHA-256	A69047B2AD2684EF4D5013ECA4627420ADBC42DCA155FBD06CE9B52FB1A67F11

Key	Value
MD5	2D40A932AA0AB6873A8454687C55D786
PackageArch	x86_64
PackageDescription	hyper 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.
PackageName	python3-hyper
PackageRelease	lp153.9.3
PackageVersion	0.7.0+git88.18b629b
SHA-1	908EE624E982E6D688A4D0E78FDFF3D285DD8197
SHA-256	F90D802C809DAA028B8DCBD65CB5800492ABC197C5B7B2C7E73F626FAABD275B