Polishing and improving codebases automatically
refine leverages the capabilities of libCST (Library for Concrete Syntax Trees), a Python
library designed for parsing, manipulating, and generating Python code in a syntax-preserving way. It builds upon libCST's
codemod module, which provides utilities for transforming code
programmatically.
Key Differentiators
Chained Codemod Execution
refine enables running multiple codemod's in a single CLI execution, streamlining workflows compared to libCST's one-codemod-per-execution approach.
Priority Management
Codemods are applied in a predefined order based on priorities defined by the modules. This ensures automatic logical sequencing of transformations.
Streamlined Features
Single-Pass Efficiency
Chained execution minimizes redundant parsing and tree-building processes, improving efficiency for large-scale projects.
Focus on Developer Productivity
By reducing the need for multiple executions, refine enhances developer workflows, especially in CI/CD pipelines or batch processing.
1 maintainer
Release files for refine 0.14.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| refine-0.14.1.tar.gz | 4.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| refine-0.14.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 MB
Release files / refine-0.14.1.tar.gz
| Download URL | refine-0.14.1.tar.gz |
|---|---|
| Size | 4.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
728c54576ab6ba10347565a41a606023844a517cc2d6ef2a4bfc0575affaba8c
|
|
BLAKE2b-256 checksum How to use checksums |
2c0e15740af309940ef8ba1ea280127693b1bc71a9301fc6fa19cf0d62d1976c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 6, 2026.
Transparency logRelease files / refine-0.14.1-py3-none-any.whl
| Download URL | refine-0.14.1-py3-none-any.whl |
|---|---|
| Size | 37.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fda19248a52a0f099599270a2974261a31bce3a7027c5d7ac87be52a41eb0bb3
|
|
BLAKE2b-256 checksum How to use checksums |
d628e4663bfd99c9de5523a8f05727dfd0ffb3289469054c2968c9ecd157cd5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 6, 2026.
Transparency log
