Conversation
|
I think that it's pretty reasonable to use the |
|
I considered it, but I thought the extra flexibility from not requiring any specific virtual environment might be useful someday. Happy to switch up the strategy here if we decide otherwise. |
rod-glover
left a comment
There was a problem hiding this comment.
Agreed that it seems reasonable to use --break-system-packages in this instance. Assuming you know that existing downstream users of this image work, I say go ahead and merge.
|
Other repositories using this docker image:
So as far as I can tell, the only two repositories that currently deploy this image are climate-explorer-backend and sandpiper, both of which have been updated to use this version. |
This PR upgrades to Ubuntu 24.04, GDAL 3.8, and Python 3.12.
Python 3.12 heavily encourages users to install libraries into a virtual environment such as
pipx,poetry, orvenv. However, in this case, which creates a single-purpose docker container as a base for specific applications, I think we are justified to use the--break-system-packagesargument to override 3.12's preferences; we're not concerned about any hypothetical other python applications getting their dependencies scrambled by a systemwide python library install.(Draft until we've verified that other applications built on top of this still work.)