fixup: Automatically add and remove python import statements
The goal is that running fixup my_file.py will automatically add or remove
import statements to or from my_file.py. This project is inspired by
autoimport, with the key difference
that manipulation of source code will be done using abstract syntax trees
instead of regular expressions.
Currently this tool pre-alpha.
Metadata
Release files for fixup 0.0.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 |
|---|---|---|---|---|
| fixup-0.0.0.tar.gz | 2.6 kB | Without provenance | Details for fixup-0.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fixup-0.0.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for fixup-0.0.0-py2.py3-none-any.whl |
Total release size: 5.3 kB
Release files / fixup-0.0.0.tar.gz
| Download URL | fixup-0.0.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab4a53d8ba301ba40904c502a7ff3739dee4da056d2370bd4af5ec827ad7a3de
|
|
BLAKE2b-256 checksum How to use checksums |
3d63440532018b6fc5fa0fe5e0a5a31eb175754a2bb0958839437bf7fe2ef6e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.27.1
|
Release files / fixup-0.0.0-py2.py3-none-any.whl
| Download URL | fixup-0.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a6da6f934d434dc11929fb26acdfcee822ea3ae81de5fc08d53f8d8edbd86378
|
|
BLAKE2b-256 checksum How to use checksums |
b893d51705b6b5dad8cc9b3de098fc105f106eb2b73c0578f5b6b5e20481c4a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.27.1
|
Security for fixup 0.0.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.