Closed joefutrelle closed 6 months ago
Note that I am installing psycopg2-binary
instead of psycopg2 source to assist with builds on platforms other than Docker--source builds were failing on my development platform. This can be revisited if the use of psycopg2-binary
causes any unanticipated issues.
No issues pulling this down and rebuilding the container. Everything appears to be functioning normally, and there were no issues with the binary version of psycoph2. For reference, I checked the library versions I had prior to the update, and the changes were minimal (further indicating things should be fine with the pinned version)
Django==4.2.5 -> 4.2.11
gunicorn==21.2.0 === 21.2.0
psycopg2==2.9.8 -> psycopg2-binary 2.9.9
numba==0.58.0 -> 0.59.1
celery==5.3.4 -> 5.3.6
pymemcache==4.0.0 === 4.0.0
redis==5.0.1 -> 5.0.3
scipy==1.11.3 -> 1.12.0
pandas==2.1.1 -> 2.2.1
h5py==3.9.0 -> 3.10.0
requests==2.31.0 === 2.31.0
Pillow==10.0.1 -> 10.3.0
rectpack==0.2.2 === 0.2.2
scikit-image==0.21.0 -> 0.22.0
pysmb==1.2.9.1 === 1.2.9.1
PyYAML==6.0.1 === 6.0.1
Pinning dependencies. Note that
requirements.txt
contains all dependencies for pyficb as well, and those are coordinated with the incoming PR on that repo. We should revisit that and address it post-release IMO.