-
Notifications
You must be signed in to change notification settings - Fork 818
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
Update Docker images to use Python 3.12 #3051
Labels
packaging
Issues with building and installing `unstructured`
Comments
MthwRobinson
added
the
packaging
Issues with building and installing `unstructured`
label
May 20, 2024
Tried this but, as seen in this job, it says
|
Looks like the issue may be
|
MthwRobinson
added a commit
to Unstructured-IO/unstructured-inference
that referenced
this issue
May 22, 2024
…r extras (#350) ### Summary First step in resolving Unstructured-IO/unstructured#3051. Per [this comment](Unstructured-IO/unstructured#3051 (comment)), we were having troubling running `unstructured` in the Python 3.12 `wolfi-base` contain due to issues related to `pycocotools`, which is only used for the legacy `detectron2` model from `layoutparser`. Since we've replaced this with `detectron2onnx`, this PR removes the `layoutparser` extra dependencies that caused issues with Python 3.12. The `layoutparser` base dependency is still required because we use layout objects from that library. It's likely we could remove these in a future iteration. Temporarily disabled the ingest tests, because they seem to have been broken for the past six months. Last commit that they passed for was [this one](0f0c2be). Opened #352 to reenable them. ### Testing If CI passes we should be good to go.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the AMD image uses Python 3.11 and the ARM image using Python 3.10. Since we support Python 3.12 as of #3047, we can now update these containers to use Python 3.12 instead. This will keep us on the latest version and reduce the risk that our build will break of Python 3.11 is dropped in
wolfi-base:latest
.The text was updated successfully, but these errors were encountered: