Django Codemod
Collections of libCST codemodder to help upgrades to newer versions of Django.
Features
This is based on libCST and implements codemods for it. This is currently very limited but the aim is to add more for helping with upcoming deprecations.
Currently implemented codemodders are listed below and grouped by the version of Django where deprecations are removed.
Not finding what you need? I'm open to contributions, please send me a pull request.
Django 4.0
All these are in the module django_codemod.commands.django_40:
ForceTextToForceStrCommand: migrate deprecatedforce_text()function toforce_str().SmartTextToForceStrCommand: migrate deprecatedsmart_text()function tosmart_str().UGetTextToGetTextCommand: migrate deprecatedugettext()function togettext().UGetTextLazyToGetTextLazyCommand: migrate deprecatedugettext_lazy()function togettext_lazy().UGetTextNoopToGetTextNoopCommand: migrate deprecatedugettext_noop()function togettext_noop().UNGetTextToNGetTextCommand: migrate deprecatedungettext()function tongettext().UNGetTextLazyToNGetTextLazyCommand: migrate deprecatedungettext_lazy()function tongettext_lazy().URLToRePathCommand: migrate deprecatedurl()function tore_path().
Django 3.2
All these are in the module django_codemod.commands.django_32:
Nothing these yet!
Django 3.1
All these are in the module django_codemod.commands.django_31:
Nothing these yet!
Django 3.0
All these are in the module django_codemod.commands.django_30:
RenderToResponseToRenderCommand: migrate deprecatedrender_to_response()function torender().
Contributors ✨
Thanks goes to these wonderful people (emoji key):
Bruno Alla 💻 🐛 📖 |
Adam Johnson 📖 |
This project follows the all-contributors specification. Contributions of any kind welcome!
Credits
This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.
Metadata
Release files for django-codemod 0.4.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 |
|---|---|---|---|---|
| django-codemod-0.4.0.tar.gz | 13.5 kB | Without provenance | Details for django-codemod-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_codemod-0.4.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for django_codemod-0.4.0-py2.py3-none-any.whl |
Total release size: 21.2 kB
Release files / django-codemod-0.4.0.tar.gz
| Download URL | django-codemod-0.4.0.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fafb8591a355660ef5e350e3441d98c38456a778005f979341e3f7dada842f51
|
|
BLAKE2b-256 checksum How to use checksums |
2e22340b8bbc01927b4302a97eeaee2a9afe17dc1acb157f7e9e4d5f08c713d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.0
|
Release files / django_codemod-0.4.0-py2.py3-none-any.whl
| Download URL | django_codemod-0.4.0-py2.py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
2fcd175be8e123a3178cf21a53cbbd2dfe531a7675d48b0c7b8c002edc419c9c
|
|
BLAKE2b-256 checksum How to use checksums |
f7e7731886c3e2d3bb3f74901f81887a44d47c82ec2b6983505719ebc52ec01e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.0
|
Security for django-codemod 0.4.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.