Skip to content

Upgrade Django 5.2#996

Merged
jsjiang merged 4 commits intodevelopfrom
969_django_5.2_upgrade
Mar 4, 2026
Merged

Upgrade Django 5.2#996
jsjiang merged 4 commits intodevelopfrom
969_django_5.2_upgrade

Conversation

@jsjiang
Copy link
Copy Markdown
Contributor

@jsjiang jsjiang commented Feb 26, 2026

@sfisher Hi Scott,
Here are the changes:

  • replace deprecated notifyAll() function with notify_all()
  • upgrade Django to 5.2.11 (the latest version in 5.2)
  • upgrade Python packages and dependencies to the latest version

Please review and let me know if you have questions.

Thank you

Jing

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR upgrades the project’s Django baseline and refreshes related Python dependencies, while updating thread-condition notifications to the modern notify_all() API.

Changes:

  • Bump Django from 4.2.27 to 5.2.11 in Poetry dependencies and regenerate poetry.lock.
  • Upgrade several runtime and dev dependencies (e.g., fasteners, filelock, lxml, xmltodict, pytest-django, pytest-mock).
  • Replace deprecated notifyAll() with notify_all() on threading.Condition instances.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
requirements-dev.txt Updates pytest-related dev dependencies.
pyproject.toml Pins Django 5.2.11 and bumps several dependency version constraints.
poetry.lock Regenerated lockfile reflecting the upgraded dependency graph.
impl/state.py Uses Condition.notify_all() instead of deprecated notifyAll().
impl/ezid.py Uses Condition.notify_all() for lock release and unpause notifications.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Copy Markdown
Contributor

@sfisher sfisher left a comment

Choose a reason for hiding this comment

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

Hi Jing,

I spent a lot of time reconfiguring my python environment and updating before I could get this working. I also had some homebrew and mysql version problems (needed 8.4 for the connection settings with our dev database).

Anyway, once I got it all working it seems ok. I did notice that in the FAQ this looks a bit weird (with big spaces after some items), but that is quite possibly a pre-existing problem probably very low priority and maybe not new to this update. (Not sure.)

Image

Seems working well to me when I tried it out on my local and also on the dev server.

@jsjiang
Copy link
Copy Markdown
Contributor Author

jsjiang commented Mar 3, 2026

@sfisher Thank you Scott for reviewing and testing. Can you take a look at FAQ on EZID Prd https://ezid.cdlib.org/learn/doi_services_faq?

@jsjiang
Copy link
Copy Markdown
Contributor Author

jsjiang commented Mar 4, 2026

Verified that the big spaces after some items in FAQ page is a pre-existing problem. Recorded the issue in a ticket #997, fix the issue in future UI related updates.

@jsjiang jsjiang merged commit 0aa6266 into develop Mar 4, 2026
6 checks 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.

3 participants