| Key | Value |
|---|---|
| FileName | ./usr/lib/python2.7/site-packages/tinyrpc/dispatch/__init__.pyc |
| FileSize | 7896 |
| MD5 | 26E66D7A03CCC9141D642452FC129620 |
| SHA-1 | 439EEEF59CAB3F2B15613C056020B33C6D803326 |
| SHA-256 | A468C33884E18EF3C496EC6301F83ABD4402D1BF24D8AA01301A092AA507162E |
| SSDEEP | 96:mQUB/kA5UU/RXSb27X9nGNGzk/kHykYuSAqWBwGLvd9wOTBzaDMtA730ZQGa2sDV:C/NUU5Xo0GQzG2TrbdAMc0SG4D9nBN |
| TLSH | T18AF183D0A2EB4393D9B99A3461B212579A57F037B1227B8574BCA8391F4D238C53FE81 |
| 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 | EABD4D2B2981C626508EDCC1C2337112 |
| PackageArch | noarch |
| PackageDescription | There are a number of jsonrpc libraries already out there on PyPI, most of them handling one specific use case (e.g. JSON via WSGI, using Twisted, or TCP sockets). None of the libraries, however, made it easy for the author of TinyRPC to reuse the jsonrpc-parsing bits and substitute a different transport (i.e. going from json via TCP to an implementation using WebSockets or ZeroMQ). |
| PackageName | python2-tinyrpc |
| PackageRelease | lp150.1.2 |
| PackageVersion | 0.9.1 |
| SHA-1 | A6C81C374C805FEFF411C10A921D1B34715200E0 |
| SHA-256 | D66D3E3E558BB7736E8E4DD365FAE283B0C4747744474FCF1A5489681A3F2BF4 |