Verilog parser for Python
Lark based parser for Verilog netlists (structural Verilog without behavioral statements). This is meant to be used to read netlists as generated by HDL logic synthesizers such as Yosys.
Example
from verilog_parser.parser import parse_verilog
ast = parse_verilog(open(verilog_file_path).read())
Install
From PyPI:
pip install verilog-parser
From git:
pip install git+https://codeberg.org/tok/py-verilog-parser
From git for development:
git clone https://codeberg.org/tok/py-verilog-parser
cd py-verilog-parser
pip install --editable .
Metadata
Release files for verilog-parser 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| verilog_parser-0.0.7.tar.gz | 7.2 kB | Without provenance | Details for verilog_parser-0.0.7.tar.gz |
Release files / verilog_parser-0.0.7.tar.gz
| Download URL | verilog_parser-0.0.7.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbe6db18bc74398fa481ca373205818065cac2ac0e165886ce373b01bdf8e0f7
|
|
BLAKE2b-256 checksum How to use checksums |
8904bda60c23525e485809cba64acdc7b90102582e73286faff0761cc49f4d63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Security for verilog-parser 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.