-
Notifications
You must be signed in to change notification settings - Fork 853
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
Version 4.3.0 not available on pypi #316
Comments
There is no official timeline. 4.3.0 cannot be compiled with the current toolchain on Linux because the Branch: https://github.com/skvark/opencv-python/tree/feat/manylinux2014 |
Hello @skvark, pretty interested in this as well. |
Same excited, especially for non-patent SIFT. |
Yeah, it just takes some time since I'm doing this on my free time which is rather limited. I'll have to port the 3.4 branch to |
How update on 4.3.0 release? Has some juicy things in it |
@skvark Anything we can do to help? Testing, etc? |
Qt5 which has been installed via CentOS package manager does not work properly or there's some config wrong somewhere. Next thing is to try custom Qt5 build to see if the error can be avoided that way. Details are at #309 |
Regarding manual build, have u look at C++ package managers? |
thank you very much for your work ! |
3.4.10 release builds are now in progress. 4.3.0 will come after they are done. |
Thanks @skvark for all of your hard work! |
macOS builds for Python 3.5 were not uploaded to PyPI due to SSL error. I'll have to check if that can be fixed somehow. However, I think it's not a big issue since 3.5 will be EOL in couple of months anyways. |
My personal opinion is that it would be fine to drop 3.5 at this point. Many packages already dropped lower than 3.6 so that they could use f-strings and variable type annotations (needed for |
When can we expect version 4.3.0 to hit pypi?
The text was updated successfully, but these errors were encountered: