Key | Value |
---|---|
FileName | ./usr/lib/python3.10/site-packages/astor/__pycache__/__init__.cpython-310.opt-1.pyc |
FileSize | 2501 |
MD5 | B2A31775BCA3F3E0931D0BA4470ECAC3 |
SHA-1 | 2B27A7E0C55CEAD7EE41E8B8E63D632A303CD2DC |
SHA-256 | CFB2539486E5B6427B6FF1015C9D7CEBABB17CEF47E4C36D678AA0B1FB77CBAD |
SSDEEP | 48:5TdhGinv2ybJoU2mN0bWEKIlM9SqRvEAdYArWgJGQUML53:5TdhG6v2ELnsHdqS4/T3 |
TLSH | T19A5142F6908E2476FDF1F2BA541B031140F0D267129FB526F92092873D5C7C822E81BC |
hashlookup:parent-total | 5 |
hashlookup:trust | 75 |
The searched file hash is included in 5 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 985C93B1C84513245AA29FB5520C6B08 |
PackageArch | noarch |
PackageDescription | astor is designed to allow easy manipulation of Python source via the AST. There are some other similar libraries, but astor focuses on the following areas: - Round-trip an AST back to Python: - Modified AST doesn't need linenumbers, ctx, etc. or otherwise be directly compileable for the round-trip to work. - Easy to read generated code as, well, code - Can round-trip two different source trees to compare for functional differences, using the astor.rtrip tool (for example, after PEP8 edits). - Dump pretty-printing of AST - Harder to read than round-tripped code, but more accurate to figure out what is going on. - Easier to read than dump from built-in AST module - Non-recursive treewalk - Sometimes you want a recursive treewalk (and astor supports that, starting at any node on the tree), but sometimes you don't need to do that. astor doesn't require you to explicitly visit sub-nodes unless you want to: - You can add code that executes before a node's children are visited, and/or - You can add code that executes after a node's children are visited, and/or - You can add code that executes and keeps the node's children from being visited (and optionally visit them yourself via a recursive call) - Write functions to access the tree based on object names and/or attribute names - Enjoy easy access to parent node(s) for tree rewriting |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python310-astor |
PackageRelease | 6.3 |
PackageVersion | 0.8.1 |
SHA-1 | 389C93757BA088C648A4C011A3FC0DAE07FD5420 |
SHA-256 | 74A84BB2B759F0C4DA18D6EE36006E75092CF5C2DCCBC79144986F2FD85041B1 |
Key | Value |
---|---|
MD5 | 3549FA9995C46AB35B2EA053126B9D91 |
PackageArch | noarch |
PackageDescription | astor is designed to allow easy manipulation of Python source via the AST. There are some other similar libraries, but astor focuses on the following areas: - Round-trip an AST back to Python: - Modified AST doesn't need linenumbers, ctx, etc. or otherwise be directly compileable for the round-trip to work. - Easy to read generated code as, well, code - Can round-trip two different source trees to compare for functional differences, using the astor.rtrip tool (for example, after PEP8 edits). - Dump pretty-printing of AST - Harder to read than round-tripped code, but more accurate to figure out what is going on. - Easier to read than dump from built-in AST module - Non-recursive treewalk - Sometimes you want a recursive treewalk (and astor supports that, starting at any node on the tree), but sometimes you don't need to do that. astor doesn't require you to explicitly visit sub-nodes unless you want to: - You can add code that executes before a node's children are visited, and/or - You can add code that executes after a node's children are visited, and/or - You can add code that executes and keeps the node's children from being visited (and optionally visit them yourself via a recursive call) - Write functions to access the tree based on object names and/or attribute names - Enjoy easy access to parent node(s) for tree rewriting |
PackageName | python310-astor |
PackageRelease | 29.4 |
PackageVersion | 0.8.1 |
SHA-1 | 12130070484E404670FF1F0413BFBA5310D1F4D3 |
SHA-256 | 944EBD25770BCE765536566B4FBF3088075D96F07D9F8641F212EBD72AAF249A |
Key | Value |
---|---|
MD5 | 9377BDA15F78238CF4783B20FEF5BC1C |
PackageArch | noarch |
PackageDescription | astor is designed to allow easy manipulation of Python source via the AST. There are some other similar libraries, but astor focuses on the following areas: - Round-trip an AST back to Python: - Modified AST doesn't need linenumbers, ctx, etc. or otherwise be directly compileable for the round-trip to work. - Easy to read generated code as, well, code - Can round-trip two different source trees to compare for functional differences, using the astor.rtrip tool (for example, after PEP8 edits). - Dump pretty-printing of AST - Harder to read than round-tripped code, but more accurate to figure out what is going on. - Easier to read than dump from built-in AST module - Non-recursive treewalk - Sometimes you want a recursive treewalk (and astor supports that, starting at any node on the tree), but sometimes you don't need to do that. astor doesn't require you to explicitly visit sub-nodes unless you want to: - You can add code that executes before a node's children are visited, and/or - You can add code that executes after a node's children are visited, and/or - You can add code that executes and keeps the node's children from being visited (and optionally visit them yourself via a recursive call) - Write functions to access the tree based on object names and/or attribute names - Enjoy easy access to parent node(s) for tree rewriting |
PackageName | python310-astor |
PackageRelease | 29.4 |
PackageVersion | 0.8.1 |
SHA-1 | C0867341D309D6E5A65AA58EDC2F8468E737BDE0 |
SHA-256 | D66C5DDA4E89296A08234876FFCD04FC7DB62E87B7B12841A1B2583E93D890A4 |
Key | Value |
---|---|
MD5 | 89C3C7D589B10078BB770FA0581CC662 |
PackageArch | noarch |
PackageDescription | astor is designed to allow easy manipulation of Python source via the AST. There are some other similar libraries, but astor focuses on the following areas: - Round-trip an AST back to Python: - Modified AST doesn't need linenumbers, ctx, etc. or otherwise be directly compileable for the round-trip to work. - Easy to read generated code as, well, code - Can round-trip two different source trees to compare for functional differences, using the astor.rtrip tool (for example, after PEP8 edits). - Dump pretty-printing of AST - Harder to read than round-tripped code, but more accurate to figure out what is going on. - Easier to read than dump from built-in AST module - Non-recursive treewalk - Sometimes you want a recursive treewalk (and astor supports that, starting at any node on the tree), but sometimes you don't need to do that. astor doesn't require you to explicitly visit sub-nodes unless you want to: - You can add code that executes before a node's children are visited, and/or - You can add code that executes after a node's children are visited, and/or - You can add code that executes and keeps the node's children from being visited (and optionally visit them yourself via a recursive call) - Write functions to access the tree based on object names and/or attribute names - Enjoy easy access to parent node(s) for tree rewriting |
PackageName | python310-astor |
PackageRelease | 29.5 |
PackageVersion | 0.8.1 |
SHA-1 | 7806B7DF9C695FBE27E923B8BE73AD3692B7216A |
SHA-256 | 2080EF5B744C09AB069CA41E8D298C343E662638FD20BE9F56294194AD8A5ADA |
Key | Value |
---|---|
MD5 | ED589EF4BDAADC4EAB8495E2085D9A70 |
PackageArch | noarch |
PackageDescription | astor is designed to allow easy manipulation of Python source via the AST. There are some other similar libraries, but astor focuses on the following areas: - Round-trip an AST back to Python: - Modified AST doesn't need linenumbers, ctx, etc. or otherwise be directly compileable for the round-trip to work. - Easy to read generated code as, well, code - Can round-trip two different source trees to compare for functional differences, using the astor.rtrip tool (for example, after PEP8 edits). - Dump pretty-printing of AST - Harder to read than round-tripped code, but more accurate to figure out what is going on. - Easier to read than dump from built-in AST module - Non-recursive treewalk - Sometimes you want a recursive treewalk (and astor supports that, starting at any node on the tree), but sometimes you don't need to do that. astor doesn't require you to explicitly visit sub-nodes unless you want to: - You can add code that executes before a node's children are visited, and/or - You can add code that executes after a node's children are visited, and/or - You can add code that executes and keeps the node's children from being visited (and optionally visit them yourself via a recursive call) - Write functions to access the tree based on object names and/or attribute names - Enjoy easy access to parent node(s) for tree rewriting |
PackageName | python310-astor |
PackageRelease | 29.4 |
PackageVersion | 0.8.1 |
SHA-1 | DFEDACB94B634C4291052E34BF35E798E64289EC |
SHA-256 | 0A0910AF6EFAD3CCA5B170F62E34CD8C82FD42B12C2AA57DF35F8D931D3E79FD |