-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version conflict in docker #199
Comments
numpy is required in a few projects
But none of them define upper-bounds for the version. Would introducing Why did this happen now? Did tensorflow 2.2 change it's requirements? |
My latest local installation has these numpy versions:
ocrd_pc_segmentation already has a hard requirement for numpy==1.18.5. |
I just checked the TF versions and was surprised to see the result:
So tf21 uses the latest TensorFlow 2.3 while tf22 uses TensorFlow 2.1. That's strange and unexpected. |
All versions of TensorFlow seem to have identical requirements for numpy:
|
It looks like that would be a working solution for all sub venvs with TensorFlow, although it unnecessarily enforces older versions of numpy also for the venvs without TensorFlow. A side note: did I ever say that TensorFlow is a nightmare? |
So this has become OCR-D/core#620. |
BTW, here's a temporary workaround for existing Docker images or native venvs:
|
This is the full traceback when calling in latest docker
ocrd/all:maximum
The text was updated successfully, but these errors were encountered: