I don't think that a documented requirement for a Python package import
warrants severity "grave". The behaviour with non "C" locales is even
documented by tesseract upstream:
https://github.com/tesseract-ocr/tesseract/wiki/4.0x-Common-Errors-and-Resolutions#error-if-locale-settings-are-not-equal-to-c
Maybe a NEWS file would be an option to let developers know that it's up
to them to set the correct environment, like so:
https://github.com/sirfz/tesserocr/issues/165#issuecomment-467773550
But this is not something that I will fix in the packaged upstream code
myself.
Regards,
Michael
_______________________________________________
Python-modules-team mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
