Update python version in API and attribution

[obulat]

Fixes

Fixes #4940 by @sarayourfriend

Description

Updates python version to 3.12 in the API and python/openverse-attribution. Some packages also had to be updated to work with the new version of Python.

Testing Instructions

The CI should pass, and the API should work as usual

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
  PRs) or the media properties generator (ov just catalog/generate-docs media-props
  for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[AetherUnbound]

A few notes before we consider merging this!

[AetherUnbound]

It looks like this package and pook were the only ones that were changed in this list, and both were pinned. Is there a specific version that should be set as the upper bound instead so these can still receive patch updates?

[obulat]

Thank you for catching these! Initially, pdm automatically updated more packages, but some of the tests with pook were failing, so I reverted most unnecessary changes manually, and some reversals resulted in pinned versions :(

[sarayourfriend]

@obulat if you noticed any issues with Pook, do you mind opening an issue upstream so I can fix it?

[AetherUnbound]

Shouldn't this be in the dev-dependencies section? Is it needed for core application code?

[obulat]

Removed in c9a8fcb

[sarayourfriend]

I was going to suggest looking at going straight to 3.13 (it is GA since last week), but Django 5.1 is required before that's possible (so #4015).

[obulat]

I was going to suggest looking at going straight to 3.13 (it is GA since last week), but Django 5.1 is required before that's possible (so #4015).

Great to know. We'll go step by step here :) Some changes in this PR's initial commits caused test failures due to pook mocks not working as expected, so we might have to debug while updating these packages.

[krysal]

I recreated the image and everything seems to be working correctly 👍

env COMPOSE_PROFILES="api" just up --force-recreate --build
just catalog/up && just api/init