Skip to content

Conversation

@davidfischer
Copy link
Member

- Upgrades to psycopg(3)
- Upgrades Django 4.2 -> 5.2
- Relies on the PR for Python 3.14
@davidfischer davidfischer requested a review from a team October 30, 2025 15:32
Copy link
Contributor

Choose a reason for hiding this comment

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

Very, very small nit: It seems that the links point to the development version of the docs. Not sure if this is intended? Definitely would block merging because of this.

Copy link
Member Author

Choose a reason for hiding this comment

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

I upgraded the docs links to the dev version on purpose so I don't have to update ~20 comments when we do a Django update. Do you think we should explicitly point to the 5.2 docs?

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm ok with leaving them pointing to the dev version, as long as we know why.

Copy link
Contributor

@jlgimeno jlgimeno left a comment

Choose a reason for hiding this comment

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

Besides my other comment, looks good!

@davidfischer davidfischer merged commit 03658ea into davidfischer/upgrade-python314 Nov 1, 2025
1 check passed
@davidfischer davidfischer deleted the davidfischer/upgrade-django-52 branch November 1, 2025 16:50
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.

3 participants