Skip to content

Add django-upgrade dependency - #1298

Merged
kingbuzzman merged 2 commits into
mainfrom
djupgrade
Aug 3, 2026
Merged

Add django-upgrade dependency#1298
kingbuzzman merged 2 commits into
mainfrom
djupgrade

Conversation

@kingbuzzman

Copy link
Copy Markdown
Member
  • Added django-upgrade==1.31.1 to the linting dependencies in pyproject.toml.
  • Updated tox.ini to include a command for running django-upgrade on specified directories.

These changes enhance the linting process by incorporating Django upgrade checks.

- Added `django-upgrade==1.31.1` to the linting dependencies in `pyproject.toml`.
- Updated `tox.ini` to include a command for running `django-upgrade` on specified directories.

These changes enhance the linting process by incorporating Django upgrade checks.
@kingbuzzman
kingbuzzman enabled auto-merge (squash) August 3, 2026 14:44
@kingbuzzman
kingbuzzman merged commit 68334fd into main Aug 3, 2026
17 checks passed
@kingbuzzman
kingbuzzman deleted the djupgrade branch August 3, 2026 14:48
@bluetech

bluetech commented Aug 3, 2026

Copy link
Copy Markdown
Member

I'm not sure django-upgrade is a good fit here, since we need to be somewhat careful about our Django usage. So normally when Django adds a deprecation warning, we handle it with a conditional or such.

@kingbuzzman

Copy link
Copy Markdown
Member Author

I'll remove it, my thought here was more so we can catch it before hand. But I see your point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants