Bump python from 3.12.5-slim to 3.13.0-slim

[dependabot]

Bumps python from 3.12.5-slim to 3.13.0-slim.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sea-kelp]

@dependabot rebase

[sea-kelp]

The build is failing while building jellyfish because the container doesn't have cargo installed:

14.53   Backend subprocess exited when trying to invoke build_wheel                                                                                                                     
14.53                                                                                       
14.53   Running `maturin pep517 build-wheel -i /tmp/tmpryyc2t6c/.venv/bin/python --compatibility off`
14.53   💥 maturin failed                                                                   
14.53     Caused by: Cargo metadata failed. Do you have cargo in your PATH?
14.53     Caused by: No such file or directory (os error 2)                                                                                                                             
14.53   Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/tmp/tmpryyc2t6c/.venv/bin/python', '--compatibility', 'off'] returned non-zero exit status 1
14.53   
14.53 
14.53   at /usr/local/lib/python3.13/site-packages/poetry/installation/chef.py:164 in _prepare
14.54       160│ 
14.54       161│                 error = ChefBuildError("\n\n".join(message_parts))
14.54       162│ 
14.54       163│             if error is not None:
14.54     → 164│                 raise error from None
14.54       165│ 
14.54       166│             return path
14.54       167│ 
14.54       168│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:
14.54 
14.54 Note: This error originates from the build backend, and is likely not a problem with poetry but with jellyfish (0.11.2) not supporting PEP 517 builds. You can verify this by runn
ing 'pip wheel --no-cache-dir --use-pep517 "jellyfish (==0.11.2)"'.

Looks like jellyfish is used by the us package:

$ just run --no-deps web poetry show --tree --why jellyfish
docker compose --file=docker-compose.yml --file=docker-compose.dev.yml run --rm "$@"
Skipping virtualenv creation, as specified in config file.
us 3.1.1 US state meta information and other fun stuff
└── jellyfish 0.11.2

[sea-kelp]

Waiting on the wheel to be released to PyPI: jamesturk/jellyfish#218

[AetherUnbound]

I'm now getting issues with installing Numpy via Poetry, I think because the wheels haven't been built for 3.13 yet 😕 We may just need to hold off on this for a bit.

[AetherUnbound]

Actually, I'm still seeing the jellyfish issue too. I'll keep looking into this.