With the current version numbers, running "docker-compose up --build" on privacy-api with Python 3.9 used in the privacy_api Dockerfile would result in a 9 to 10 minute wait for "pip install" to complete. This appears to be due to older cython / spacy / grcpio / protobuf dependencies. I upgraded each of these to the latest minor version available, along with bumping up tldextract to its latest bugfix version. I left knack and regex alone.
Another issue this solves is that when running "pip install -e . --no-cache-dir" on this project with Python 3.9.x, the install would fail. Upgrading cython to the latest minor version fixed this problem.
I cannot verify if these upgrades break anything, but they do solve my immediate problem of trying to run privacy-api on Python 3.9 - and without having to wait 10 minutes for "pip install" to complete within docker-compose. I am hoping that by sticking to bugfix / minor upgrades, we will not encounter any breaks due to backwards incompatibility issues.
With the current version numbers, running "docker-compose up --build" on privacy-api with Python 3.9 used in the privacy_api Dockerfile would result in a 9 to 10 minute wait for "pip install" to complete. This appears to be due to older cython / spacy / grcpio / protobuf dependencies. I upgraded each of these to the latest minor version available, along with bumping up tldextract to its latest bugfix version. I left knack and regex alone.
Another issue this solves is that when running "pip install -e . --no-cache-dir" on this project with Python 3.9.x, the install would fail. Upgrading cython to the latest minor version fixed this problem.
I cannot verify if these upgrades break anything, but they do solve my immediate problem of trying to run privacy-api on Python 3.9 - and without having to wait 10 minutes for "pip install" to complete within docker-compose. I am hoping that by sticking to bugfix / minor upgrades, we will not encounter any breaks due to backwards incompatibility issues.