Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop support for Python 3.6-3.7, Django 3.2-4.1 #69

Merged
merged 9 commits into from
Feb 15, 2025

Conversation

browniebroke
Copy link
Contributor

@browniebroke browniebroke commented Feb 14, 2025

Fix #47

They're all EOL:

https://endoflife.date/python

image

…gnored, please remove it to avoid potential confusion
Copy link
Owner

@tbicr tbicr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, LGTM with few changes:

  • I'd propose to remove django 3.2, 4.0, 4.1 and python 3.6, 3.7, ie. keep 3.8 for now
  • can you bump new packet version in django_zero_downtime_migrations/init.py
  • can you add changes to CHANGES.md

tox.ini Outdated
py{3.6,3.7,3.8,3.9,3.10}-django{3.2}
py{3.9,3.10,3.11,3.12}-django{4.2}-psycopg{2,3}
py{3.9,3.10,3.11}-django{4.0,4.1}
py{3.9,3.10}-django{3.2}
Copy link
Owner

@tbicr tbicr Feb 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we:

  • remove django 3.2 with python 3.6-3.7
    • will require django.VERSION[:2] <= (3, 2) branch removal
  • remove django 4.0 and django 4.1
    • will require django.VERSION[:2] < (4, 0) and django.VERSION[:2] >= (4, 0) branch removal
    • will require django.VERSION[:2] < (4, 1) and django.VERSION[:2] >= (4, 1) branch removal
    • will require django.VERSION[:2] < (4, 2) and django.VERSION[:2] >= (4, 2) branch removal
    • will require # TODO: after django 4.1 support drop replace *args, **kwargs with original signature comment removal and signature fix
  • keep django 4.2 and keep python 3.8, ie. postpone python 3.8 removal with django 4.2 removal or when it will became blocker

@browniebroke browniebroke force-pushed the drop/python-3.6-3.8-support branch from b187220 to dee9fa9 Compare February 15, 2025 13:29
@browniebroke
Copy link
Contributor Author

  • can you bump new packet version in django_zero_downtime_migrations/__init__.py

To 0.17 I assume?

@@ -955,49 +955,27 @@ def _patched_iter_column_sql(
):
yield self.connection.ops.tablespace_sql(tablespace, inline=True)

if django.VERSION >= (4, 1):
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one was automatable with django-upgrade, unlike the other branches where the version is specified as django.VERSION[:2]

probably one to keep in mind for the future where adding these kind of branches: https://github.com/adamchainz/django-upgrade?tab=readme-ov-file#versioned-blocks

@browniebroke browniebroke changed the title Drop support for Python 3.6 - 3.8 Drop support for Python 3.6-3.7, Django 3.2-4.1 Feb 15, 2025
Copy link
Owner

@tbicr tbicr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, can you also drop python 3.6 and 3.7 from Dockerfile?

@tbicr tbicr merged commit 08e56ea into tbicr:master Feb 15, 2025
1 check passed
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.

Drop support for Python 3.6
2 participants