Key | Value |
---|---|
FileName | ./usr/lib/python3.10/site-packages/trio/tests/__pycache__/test_threads.cpython-310.opt-1.pyc |
FileSize | 21062 |
MD5 | 8D5E1E0E1625AEFB1CFFFF663944CA35 |
SHA-1 | 041D4EFD9FE9E981E3EDCF1F77F91E3D17594B3D |
SHA-256 | B23CA75C0AAB3300368D2A44B696F71A1131CD61B1F61F7FFAA0C37D2EFB3762 |
SSDEEP | 384:5l8kyKVeQU1zdRV7wS2EwYhJ20/dCuiBQiSNoyL:5Xy9QU1JRx8EFrXdCeiSR |
TLSH | T17B9234B2696A09B6FDB2F7FDCC1E0320C617A21153999013D517E0CE5D4DBCDACA81A9 |
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 | 21CDD3EBC815043ABD664CE4CBE01EE6 |
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 | neoclust <neoclust> |
PackageName | python3-trio |
PackageRelease | 1.mga9 |
PackageVersion | 0.21.0 |
SHA-1 | AB6178E2A4DEBE86E95D77719DB35AE5E799C04C |
SHA-256 | 3F90AA87AEB207CCA15DE06337D61FB489B89DBCB037A0F7A6BBD22E6FAF7CAD |