python3.8 is out

[hyunlee1o]

Could you add support to it please?

[skvark]

3.8 builds will be added when the whole toolchain supports it. Afaik Appveoyr does not have Python 3.8 available but I hope it will be added soon: https://www.appveyor.com/docs/windows-images-software/#python

Manylinux added support yesterday: pypa/manylinux@f9ef816

macOS is also ok: matthew-brett/multibuild@8c8d6e6

[skvark]

appveyor/ci#3142

[cclauss]

Given that AppVeyor seems to be asleep at the wheel on Python 3.8, does it make sense to shift the Windows tests to Travis or others?

[maximveksler]

We should see which CI gets there first. Another option is manually installing and compiling python before building the wheel. That's a workaround, but highly impractical one.

https://github.com/microsoft/azure-pipelines-image-generation/issues/1317

[cclauss]

Travis already supports Python 3.8 on Linux and Windows: https://docs.travis-ci.com/user/languages/python/#running-python-tests-on-multiple-operating-systems

[skvark]

Pull requests are welcome. However, there seems to be a fast workaround now appveyor/ci#3142 (comment). It's quite a lot faster to implement the workaround than to setup the Travis Windows support.

[hugovk]

🚀 Python 3.8 is now available on AppVeyor:

• Python 3.8.0 appveyor/ci#3142 (comment)

[cowlinator]

@skvark , can we expect work on Python 3.8 support to begin soon?

[Rukario]

I've waited for 3.8 support...

[skvark]

Python 3.8 wheels will be released when I have the time to fix the builds. multibuild upgrade broke something and that needs to be fixed to get the macOS & Linux builds working. Appveyor is not a blocking issue, I would have already released new version without these additional issues.

[yangspeaking]

waiting for 3.8 support. Thanks for the effort!

[ygwangthu]

wait too :-)

[skvark]

It seems that I found the multibuild issue and the pre-build stage proceeds now normally. I hope that I get new releases out during this week.

Just a heads up for those who might be still using Python 3.4: it's in EOL and I will drop it from build matrix so no new releases coming for 3.4 anymore. Python 2.7 will be also dropped by the end of this year.

[ofersadan85]

Just a heads up for anyone looking for unofficial pre built wheels for python 3.8, you can find them here: https://www.lfd.uci.edu/~gohlke/pythonlibs/#opencv

(Windows only as of this moment, either 32 or 64 bit)

[viponedream]

Just a heads up for anyone looking for unofficial pre built wheels for python 3.8, you can find them here: https://www.lfd.uci.edu/~gohlke/pythonlibs/#opencv

(Windows only as of this moment, either 32 or 64 bit)

i download a wheel file from that site and install, but it says:
ERROR: Could not find a version that satisfies the requirement opencv_python-4.1.2-cp38-cp38-win_amd64 (from versions: none)
ERROR: No matching distribution found for opencv_python-4.1.2-cp38-cp38-win_amd64

[skvark]

3.4.8 wheels will be in PyPI during the next 20 hours. 4.1.2 will follow tomorrow when 3.4.8 builds have finished.

@viponedream This is not a support forum for Gohlke's custom wheels. They are not related to this repository. Please ask your question for example at Stack Overflow.

[skvark]

Most of the 4.1.2 wheels with Python 3.8 support are now available in PyPI. Some Windows wheels are still building, but they will be done in the next few hours.

[HEBOS]

Shall we have aarch64 too?

[skvark]

ARM support in the Python packaging ecosystem is not yet mature. For example, there a no ARM wheels for numpy in PyPI (OpenCV build depends on numpy).

There are open issues about ARM builds for different Python projects (including this project: #13). For more information, see following issues:

• ARM builds? ARM builds? pypa/manylinux#84
• Why does warehouse allow linux_armv6l and linux_armv7l wheels? Why does warehouse allow linux_armv6l and linux_armv7l wheels? pypi/warehouse#3668

[sol-prog]

@skvark I think the armv6l and armv7l wheels are meant for Raspberry Pi and BeagleBone Black users. For example RPi Zero needs armv6l wheels, RPi 2 and up use the armv7l wheels.

[HEBOS]

What about Jetson? Sent from my Samsung Galaxy smartphone.

…

-------- Original message -------- From: Paul Silisteanu <notifications@github.com> Date: 25/11/2019 19:11 (GMT+01:00) To: skvark/opencv-python <opencv-python@noreply.github.com> Cc: Hrvoje Matić <hmatic5@outlook.com>, Comment <comment@noreply.github.com> Subject: Re: [skvark/opencv-python] python3.8 is out (#253) @skvark<https://github.com/skvark> I think the armv6l and armv7l wheels are meant for Raspberry Pi and BeagleBone Black users. For example RPi Zero needs armv6l wheels, RPi 2 and up use the armv7l wheels. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#253>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEUHQAGFLC7V2P5BQNKFASTQVQIM3ANCNFSM4JBD4BOQ>.

[skvark]

@sol-prog Yes, I know (also many other devices are running on armv6, armv7, armv8 architectures like most of the worlds smartphones). You can get custom ARM wheels for Raspberry Pi from https://www.piwheels.org/. And please note that they work reliably only on Raspberry Pi.

@HEBOS As I wrote, you need to wait that the upstream projects and infrastructure supports building ARM wheels with reasonable effort. Currently it's not possible. However, you can always build opencv-python from sources locally on your device: clone this repository and run python setup.py bdist_wheel.