Result for 062C85170D3B33AEE6A178B96A769D4701266C19

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/Pyro4/constants.pyo
FileSize478
MD5BEFB325F2535275ECE785A8A49DBC4E2
SHA-1062C85170D3B33AEE6A178B96A769D4701266C19
SHA-256498597D4DE89D1E8F0327A5E413C9A1D3753EBE2F6CB8FB2AFB8F2F7B8FAE490
SSDEEP12:hCeXQUtexoch63c3gqCziqKKqID6Iy4rlItKr2jLw958iYfzRxHaUm:hZ26s3aP3lItBLwHFYLRG
TLSHT110F05CC8A7968152EB7B47B2E9222017884A91776208E9C1A919F0BE15DA94B4D3F351
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
MD5714F1CAEB08050255C5A4FD880CE3E51
PackageArchnoarch
PackageDescriptionPyro provides an object-oriented form of RPC. You can use Pyro within a single system but also use it for IPC. For those that are familiar with Java, Pyro resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or RMI. Pyro4 is a reimplementation of the original pyro, that was begun in 2010. According to upstream, pyro4 can now be considered the new ‘main’ Pyro version. Since it is not API compatible to pyro-3.x, the package was renamed to Pyro4
PackageMaintainerumeabot <umeabot>
PackageNamepython-pyro415
PackageRelease8.mga7
PackageVersion4.15
SHA-17DFC94931AA2823A5896D05300D79F51A9110A1E
SHA-2562E2C4BA7A3A2CF316CAF13F4A27D527B37B144FE94E3DDFF8A978590163D46CC