fix: handle invalid tessdata folder

[PatrickDaG]

The newest tesseract version returns an error and exits when encountering invalid tessdata-dir. This makes these tests fail. The only tests that would still work would be to set tessdata-dir to a new empty folder, but that would mean making and then deleting that folder, for what I think is negligible benefit.

[stefan6419846]

Shouldn't we gracefully handle this in pytesseract instead and keep a variant of these tests? Just removing them does not feel right. The handling should probably depend on the Tesseract version as well.

[PatrickDaG]

I must admit I'm not using pytesseract so I don't know if this library depends of gracefully handling /dev/null as a tessdata folder, otherwise I'm not seeing the benefits of keeping tests related to undocumented, and not stable behaviour of tesseract.

[bozhodimitrov]

I am not ok with removing invalid path testing.
Please reconsider contributing something that might handle the new behavior of the new tesseract version.
For sure it can be adapted. If there is a stable OS version that supports such recent tesseract version, we can add it to the CI and adjust to the new changed behavior.

[PatrickDaG]

I've tried my best, to make it work and gracefully handle errors. I must admit it isn't perfect but its about as far as my limited pytest and pytesseracte knowledge gets me.

[bozhodimitrov]

Thank you for trying. Unfortunately it alters some of the current behavior and if Tesseract is not installed it will not say it.
I might adjust the patch later, since I work on another fix at the moment.