Python _ __ ___ __| |___ _ _ _ _ (_)______ | ' \/ _ \/ _` / -_) '_| ' \| |_ / -_) |_|_|_\___/\__,_\___|_| |_||_|_/__\___|
python-modernize is a very thin wrapper around lib2to3 to utilize it to make Python 2 code more modern with the intention of eventually porting it over to Python 3. This is an unofficial fork (of https://github.com/mitsuhiko/python-modernize) that runs on both Python 2 and 3.
It does not guarantee, but it attempts to spit out a Python 2/3 compatible codebase.
Unicode Literal Control:
By default modernize will leave literals alone.
The --future-unicode flag imports the unicode_literals from the __future__ module. This requires Python 2.6 and later and will require that you mark bytestrings with b'' and native strings in str(b'') or something similar that survives the transformation.
Installation
From pip:
$ pip install --upgrade modernize3k
Usage
Preview changes on a file or directory:
$ python-modernize example.py
Write the changes:
$ python-modernize --write example.py
Modify doctests rather than normal code:
$ python-modernize --write --doctests example.py
Tests
The tests use cram:
$ cram --indent=4 test.cram
1 maintainer
Metadata
1 maintainer
Release files for modernize3k 0.5
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 |
|---|---|---|---|---|
| modernize3k-0.5.tar.gz | 8.4 kB | Without provenance | Details for modernize3k-0.5.tar.gz |
Release files / modernize3k-0.5.tar.gz
| Download URL | modernize3k-0.5.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d480353175523576452f5aa31510dfa931faf3bae12b0fd9c21ce86debc7e6f
|
|
BLAKE2b-256 checksum How to use checksums |
6a133b4b12b697ac776685adb17d680a9246b852bf26e1794762bf5bcf98e3cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for modernize3k 0.5
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.
