Ethereum Improvement Proposal (EIP) Processor
CLI tools and Python library for interacting with EIPs from the source EIPs GitHub repository.
Features/TODO
Frontend
- CLI tools
- Library API
- Documentation
Data processing:
- EIP Metadata processing
- EIP relationships and references
- Automated tagging
- File history, changelog
- Aggregate data, statistics, and error detection
- Indicate document deletion in some fashion (file flag, and empty props?)
Usage
Show EIP
eips show 712
Show EIP Headers
eips show -i 4626
Show ERC
eips show 20
API Usage
Get an EIP
>>> from eips import EIPs
>>> eips = EIPs()
>>> eip_20 = eips.get(20)[0]
>>> eip_20.title
'Token Standard'
Get all EIPs
>>> from eips import EIPs
>>> eips = EIPs()
>>> for e in eips.get():
... print(e.eip_id)
...
2018
5216
999
606
[...]
Get count of EIPs
>>> from eips import EIPs
>>> eips = EIPs()
>>> eips.len()
687
Get EIPs aggregate stats
>>> from eips import EIPs
>>> eips = EIPs()
>>> eips.stats().total
687
>>> eips.stats().errors
0
>>> [c.value for c in eips.stats().categories]
['ERC', 'Core', 'Interface', 'Networking']
>>> [s.value for s in eips.stats().statuses]
['Stagnant', 'Last Call', 'Withdrawn', 'Final', 'Review', 'Draft', 'Living']
>>> [t.value for t in eips.stats().types]
['Standards Track', 'Meta', 'Informational']
Development
Run Tests
hatch run test
Linting
hatch run lint
Release
To release, create and publish a GitHub package release
# Bump the version major/minor/patch
hatch version patch
# Tag the git commit with the version
git tag -a "v$(hatch version)" -m "v$(hatch version)"
# Push it up to GH, don't forget the tag
git push --follow-tags
Now create a GitHub release and CI will do the rest.
Metadata
Release files for eips 0.2.0
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 |
|---|---|---|---|---|
| eips-0.2.0.tar.gz | 14.4 kB | Without provenance | Details for eips-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eips-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for eips-0.2.0-py3-none-any.whl |
Total release size: 30.5 kB
Release files / eips-0.2.0.tar.gz
| Download URL | eips-0.2.0.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13a1273472d7e5afc9854f3c358b93d62bdbe4a318774808b944cb679f57bf9b
|
|
BLAKE2b-256 checksum How to use checksums |
a32dc720c14580b0b5dc5564860f326d7783cefd60a829d81ad1c1636e336140
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / eips-0.2.0-py3-none-any.whl
| Download URL | eips-0.2.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
584d0b91d40dbecf84204383307869c73db6b60bcccb08f493fbd3d3d7ef30d1
|
|
BLAKE2b-256 checksum How to use checksums |
1257b4fafdc2f458166dde0fb586ff429c643db807338a69e49fc74ea1791ec6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for eips 0.2.0
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.