Key | Value |
---|---|
FileName | ./usr/lib/python3.1/site-packages/ply/__init__.pyo |
FileSize | 180 |
MD5 | 6CFB416E4A31D50213D195DFD7EF2A21 |
SHA-1 | 21E70C9494068BA7D932A15608D300D0E7C09CDF |
SHA-256 | AF3D5446E585BDB202AD90D6C3BFF34C21E30D1617D7D6C92A293595AA8CD77E |
SSDEEP | 3:1mlNlG1/2+6c/z0cUERe4ZN/ll3tNltQdQQM9YJNQAoWrzrKRKQRTZIaBitn:kW1/2NQ0weuVllYd69YJvDrnKRKQJZIf |
TLSH | T136C08C54673D0AC3E2E9CB30B702021AC98375237E0BA5437554159A5D882AA453B909 |
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 | 20462037D48B7930C022FDD119584327 |
PackageArch | noarch |
PackageDescription | PLY is a straightforward lex/yacc implementation. Here is a list of its essential features: * It is implemented entirely in Python. * It uses LR-parsing which is reasonably efficient and well suited for larger grammars. * PLY provides most of the standard lex/yacc features including support for empty productions, precedence rules, error recovery, and support for ambiguous grammars. * PLY is straightforward to use and provides very extensive error checking. * PLY doesn't try to do anything more or less than provide the basic lex/yacc functionality. In other words, it's not a large parsing framework or a component of some larger system. |
PackageMaintainer | Fedora Project |
PackageName | python3-ply |
PackageRelease | 3.fc14 |
PackageVersion | 3.3 |
SHA-1 | C9F0D4EE047CAC6FC5C11B2C4538D007C638F0A8 |
SHA-256 | 57AA64B532A5F3E68D47A0F6C61F2FF7B9923849BB626239E48527A6AB5A0BB5 |