Result for 9531C7C4D42A527CDBEEE602EDE88E3E5AF7B5FD

Query result

Key Value
FileName./usr/lib64/python2.7/site-packages/wrapt/__init__.pyc
FileSize1179
MD54936062588CE60A29C07C874E0A46968
SHA-19531C7C4D42A527CDBEEE602EDE88E3E5AF7B5FD
SHA-256DC40E6FFC15F69F5A5261CB9129BAA6438517D3FA332A5AE6D5C1B5F7AD9F192
SSDEEP24:95a8FsYrvPdif1rQn1Ey4i8EI0UKAjVqGswUjV7qWL0XY:fcYrtiu4i8ecbh/WL4Y
TLSHT1D3210DC678B8FA67853B2B3CA0C6011B8634B37A21406445119CA1FD2FA326BC7BA71D
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
MD5251B47EBF9C2DF50ADA5D61B6E343231
PackageArchx86_64
PackageDescriptionThe aim of the **wrapt** module is to provide a transparent object proxy for Python, which can be used as the basis for the construction of function wrappers and decorator functions. The **wrapt** module focuses very much on correctness. It therefore goes way beyond existing mechanisms such as ``functools.wraps()`` to ensure that decorators preserve introspectability, signatures, type checking abilities etc. The decorators that can be constructed using this module will work in far more scenarios than typical decorators and provide more predictable and consistent behaviour. To ensure that the overhead is as minimal as possible, a C extension module is used for performance critical components. An automatic fallback to a pure Python implementation is also provided where a target system does not have a compiler to allow the C extension to be compiled. Documentation ------------- For further information on the **wrapt** module see: * http://wrapt.readthedocs.org/
PackageNamepython-wrapt
PackageRelease1.12
PackageVersion1.10.6
SHA-1DD9784AC69F8F71B1A773A017217C794496C732C
SHA-256A8B8768B2A2D7A929AC806E39E79282B37D1F1238D2A15CBED34773B65EC5E20