-
Notifications
You must be signed in to change notification settings - Fork 255
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
does not compile against libtesseract anymore #259
Comments
The above was Python 3.6 / Tesseract v5.0.0-alpha-622-g7d94 / gcc 7.5.0. I get the same on Python 3.7 / Tesseract v5.0.0-alpha-626-gddb6 / gcc 8.3.0. Cython is the newest 0.29.23. |
Backwards compatible here means that it must work with the official releases (4.1.1). And it must work with the latest releases of Tesseract 5.0. |
No, it used to be that tesserocr is compatible with a wide range of Tesseract versions, if necessary differentiating them with ifdefs to encapsulate differences to the Python user. But 8a98bf4 introduced a blanket condition |
I don't think that it is necessary that Tesserocr supports old or intermediate revisions of Tesseract which are completely unsupported (and buggy). |
tesseract 5 is still in development so tesserocr cannot guarantee compatibility since it can break at any moment, all stable releases >=3.04 are supported and so will version 5 once it's released. |
Tesseract master seems to have been supported by tesserocr for a long time, though, despite the extra effort. Especially during the long time after LSTMs had been (hastily) integrated. And at least trying to support the alpha is not just a matter of convenience: many projects depend on the Python bindings to test and advance new features. Why is this being turned down so lightly? (It should be easy for those who made the respective changes in Tesseract recently to differentiate APIs by exact version.) Also, I still see this as the most pressing problem here:
|
With the current master, I cannot
pip install
anymore:Is my Tesseract too old (i.e. have there been breaking API changes recently in Tesseract 5) perhaps?
The text was updated successfully, but these errors were encountered: