Key | Value |
---|---|
FileName | ./usr/share/doc/python-pyro415/doctrees/servercode.doctree |
FileSize | 82376 |
MD5 | 3BDAEF0789AD29A0E228838501FF7922 |
SHA-1 | 07A6A0A43ED2256D8ABB4FB1537D6C4853DE3323 |
SHA-256 | 364EBE5E8AAF04692670644265547E936DD326591845A4FA470B8A521D8A97CB |
SSDEEP | 1536:JX9IOLbdDmJkrDReQgGVyjdyfGD7wnxjGljlpx6LwyG7une1VcIlA85Qb:7IOLbdDmxx6Lwb7rcIlhk |
TLSH | T18C83EA3B3A00726B65964722287DD381F75BC36B77395C4342BCC1FE22DA36E91A95E0 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
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 |
---|---|
MD5 | 714F1CAEB08050255C5A4FD880CE3E51 |
PackageArch | noarch |
PackageDescription | Pyro 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 |
PackageMaintainer | umeabot <umeabot> |
PackageName | python-pyro415 |
PackageRelease | 8.mga7 |
PackageVersion | 4.15 |
SHA-1 | 7DFC94931AA2823A5896D05300D79F51A9110A1E |
SHA-256 | 2E2C4BA7A3A2CF316CAF13F4A27D527B37B144FE94E3DDFF8A978590163D46CC |