Result for 2B7D01915244586ACB3F95E3611752930216FAB8

Query result

Key Value
FileName./usr/share/doc/python-stestr-doc/html/api.html
FileSize11384
MD5CFB8B260501CC5EE5AD9CDE6EC7948A8
SHA-12B7D01915244586ACB3F95E3611752930216FAB8
SHA-2569F9A8399F6BE5376DCF3D701B61561F8B04E06DF2E43743A2204B28D221B3E3C
SSDEEP192:iQ5+EnhDrVDZVjA0eIjnV5eYd1M/OCkSRURWmFzKvLZrIn1DA:i+nhHVDHJeIjjdoOCZUYmUZUn1M
TLSHT1DF32852240FB9A33402352CAA2AA1B2975D3863BD15B064171FC57BD0BE7F54F917B2E
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
FileSize39116
MD5373F2737A15D4F9964261CB72F4F9001
PackageDescriptiontest runner similar to testrepository - doc Stestr stands for Slim/Super Test Repository. It is a fork of the testrepository that concentrates on being a dedicated test runner for Python projects. The generic abstraction layers which enabled testr to work with any subunit emitting runner are gone. Stestr hard codes python-subunit-isms into how it works. The code base is also designed to try and be explicit, and to provide a Python API that is documented and has examples. . While stestr was originally forked from testrepository it is not 100% backwards compatible with testrepository. At a high level the basic concepts of operation are shared between the 2 projects but the actual usage between the 2 is not exactly the same. . This package contains the documentation.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-stestr-doc
PackageSectiondoc
PackageVersion2.1.0-2
SHA-13BA0500A044674F1F046B0901A0407A12A86711B
SHA-25608B0AD3529C620140C8E621021047CF820B121A632AE300EDA38D329D9BB66CF