Key | Value |
---|---|
FileName | ./usr/lib/python3.10/site-packages/trio/_subprocess_platform/__pycache__/waitid.cpython-310.pyc |
FileSize | 2075 |
MD5 | 98B30491D7B303EFDC728BD482C21EEC |
SHA-1 | 0763F08D239E5A1095BF5978103FAB2D5521C6D0 |
SHA-256 | 8D0F524F44628BB09A11CB347E2B18C6F48B04699520AEF7C5EB7AC236D41876 |
SSDEEP | 48:LTz/jDMwvaN5wfTsuzRpSuG7DyzF54WuscxlOzV2eZImxK:LviUJzRpShuf4rPe6mxK |
TLSH | T10A4178C36F3D8B7AFC94F774A125221159E1E13E4742B0217D04D4772F0E09196F4B99 |
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 | 3BDA440F7E52CDBC6B47588934D50405 |
PackageArch | noarch |
PackageDescription | The Trio project's goal is to produce a production-quality, permissively licensed, async/await-native I/O library for Python. Like all async libraries, its main purpose is to help you write programs that do multiple things at the same time with parallelized I/O. A web spider that wants to fetch lots of pages in parallel, a web server that needs to juggle lots of downloads and websocket connections at the same time, a process supervisor monitoring multiple subprocesses... that sort of thing. Compared to other libraries, Trio attempts to distinguish itself with an obsessive focus on usability and correctness. Concurrency is complicated; we try to make it easy to get things right. |
PackageMaintainer | guillomovitch <guillomovitch> |
PackageName | python3-trio |
PackageRelease | 1.mga9 |
PackageVersion | 0.22.0 |
SHA-1 | C074D009D58CF1C18FCA6E08DD3C48645BA6726C |
SHA-256 | FB3CE511F8365BBDC1B86121FD1504DFFB8D9432BF74C383A048326C7F80F9B8 |