Key | Value |
---|---|
FileName | ./usr/lib/python3.8/site-packages/smmap/__pycache__/__init__.cpython-38.opt-1.pyc |
FileSize | 558 |
MD5 | E41455EB84D69D1695B760DB385E6ECB |
SHA-1 | 4D0433A5A4E1FB96ACA91D9B686838F497113131 |
SHA-256 | C387E004B4BE1B0005046F8FF5385449099EBACE299F03828515091F11E29CD6 |
SSDEEP | 12:M74sZLPfk0Z1akQq1acqrWiDwMB+CQPRJ1TGW+3y4v:Mj1fjZGfjDwMICWi |
TLSH | T1F6F00521C540DF37FD11F7783055672707F10875EB0A51A2B7089299ED0D2449763C12 |
hashlookup:parent-total | 6 |
hashlookup:trust | 80 |
The searched file hash is included in 6 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 0B78723EC5E81953767D08A14F724452 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python38-smmap |
PackageRelease | 1.4 |
PackageVersion | 4.0.0 |
SHA-1 | 7E2B8BFC62A62C267C593D4EB0089640E1621E19 |
SHA-256 | B5C5F035C44306C88BD335BD8E563A1C3E43652A475008AE5C743115FC55F20A |
Key | Value |
---|---|
MD5 | 6A4848EAFCBA180005DA41C2FE47E499 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python38-smmap |
PackageRelease | 34.13 |
PackageVersion | 4.0.0 |
SHA-1 | FB660C82FB4A9AB2D4CDE5B94B92FE2C50CB76DB |
SHA-256 | FE6357CC961A4ADBEE0AC963A985865C7E0FA36E2DF31E7607D7CA5D8EFA1A15 |
Key | Value |
---|---|
MD5 | 6C9BB5FBFB8011D4C4B2BA21D15E20CE |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python38-smmap |
PackageRelease | 34.12 |
PackageVersion | 4.0.0 |
SHA-1 | C8B01FD5A379065C97E1EFC227C0C5706A7A4B2D |
SHA-256 | 30919EF19C962B673167CF717187E81DF50D16FBC85E9F7AD4D362EF3F02E86C |
Key | Value |
---|---|
MD5 | D57AF2C63B2ACA006E43677959C9B81E |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python38-smmap |
PackageRelease | 34.17 |
PackageVersion | 4.0.0 |
SHA-1 | 057EFC9971FF46798195D737A697413055041E6E |
SHA-256 | EC2AEFFF6888CA3FFB7DBDFE3029808FEB1F78489355A5B78F1D00BD3FECC867 |
Key | Value |
---|---|
MD5 | 9F192C94EB1A2FEDB6A8E658A5FB1517 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python38-smmap |
PackageRelease | 34.16 |
PackageVersion | 4.0.0 |
SHA-1 | C68C30BF4D569EF23BCE6F4257825A913ECB199A |
SHA-256 | 4B385062A22F62E1BFF25B3C016AB725ACC4269652380C9097EC96877C9C7549 |
Key | Value |
---|---|
MD5 | D6121B79C0755BF6C76DF4C173045C42 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python38-smmap |
PackageRelease | 34.24 |
PackageVersion | 4.0.0 |
SHA-1 | 8BF4B3D8705696F88462BC5B142E50B123FFDE15 |
SHA-256 | 10EAC5E1021452B3512A0A119DFE144BD7279C83B1A07E30D3134373540BE3E7 |