AP-859 pytesseract worker update - #5
Conversation
- adds pytesseract dependency - updates some volumes in docker-compose - note: directly imports run_tesseract which is not explicitly exported by the pytesseract package
anarchivist
left a comment
anarchivist
left a comment
There was a problem hiding this comment.
rw+c; the main thing to fix is mounting the app within the flower container.
| } | ||
|
|
||
| try: | ||
| run_tesseract(**kwargs) |
There was a problem hiding this comment.
I assume that we are avoiding run_and_get_output because it stores the result in memory instead of on disk. And I assume image_to_pdf_or_hocr doesn't allow us to customise the output path?
Just want to make sure that I'm understanding the rationale for using a private/undocumented API.
There was a problem hiding this comment.
You are correct and it is possibly a little brittle because of it.
There was a problem hiding this comment.
yep, that's correct - the return_bytes parameter that gets set basically means "should I return bytes or str?"
there was some discussion on the potential signature of run_tesseract as "possibly changing year to year" in an issue on the pytesseract repository, but a maintainer made that comment in 2018. the signature hasn't changed in 7 years.
3 participants
Uh oh!
There was an error while loading. Please reload this page.