-
Notifications
You must be signed in to change notification settings - Fork 24
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
possible built failures on Python 3.11? #18
Comments
thanks for the report. not sure what's happening here - but seems like an c++ issue (besides some warnings about incorrect setup files). I'll try to reproduce - but that may take some time |
Is this helpful? sirfz/tesserocr#298 (comment) something to do with autogenerated code, waiting for "Cython to support Python 3.11"... |
I think this fixes building on Python 3.11. Fixes cheind#18.
In case folks find their way here, a quick fix to get your
(see #19 for details) |
* remove outdated tests * remove nose and add pytest * remove unused import * rename torch_unet to unet * format * linting * remove gpu profiling script this can be now acheived with the lightning profiler * lint with ruff and format with black * format tests * sort import with ruff and update CI workflow * remove duplicate event * black v23.3.0 * format * remove 3.11 support due to lapsolver issue cheind/py-lapsolver#18 * remove tf metric script test * run a minimal subset of pytests
should be fixed with latest pybind11 version bump |
Upcoming Fedora 37 has Python 3.11rc2 right now. I tried to install
lapsolver
with pip. There was no.whl
(but maybe this is normal for pre-release, I'm not expert on Python packaging!).Instead it tries to use the .tar.gz and fails:
The text was updated successfully, but these errors were encountered: