-
Notifications
You must be signed in to change notification settings - Fork 253
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
Couldn't import tesserocr, because locale check error #137
Comments
tesseract 4 requires In my local tests it seems to have no effect with Python 2.7 but crashes with Python 3.6 and 3.7. I'm reluctant to hard-code this into tesserocr because I'm not sure what the effect would be on other modules or Python's behavior. Maybe someone with more knowledge about this can chip in? |
As you said, the hardcoding is undesirable. IMO, I think that it is necessary to ask the Cython community about handling environment variables. cf. 24.2. locale — Internationalization services — Python 3.7.0 documentation FYI, other Language's solution. Various fixes for Tesseract 4 beta.3 · ropensci/tesseract@2784542 |
Changing locale before and after calling |
According to tesseract-ocr/tesseract/issues/1670, this might only be temporary until they replace function calls which rely on locale settings. I'd rather wait and see how this plays out before pushing any patches. |
This has been fixed in tesseract 4.1 |
I got a import error.
This error was caused by locale check.
Please see commit .
Simple workaround here .
I think that it is necessary to add the code somewhere in the appropriate place.
Environment:
In addition, I avoid install error by #129 workaroud.
The text was updated successfully, but these errors were encountered: