Discussion:
[PyQt] Versioning wheels
Eduard Babayan
2018-11-21 15:50:32 UTC
Permalink
Hello

Starting from pyqt5 version 5.7 wheels now include 2 versions. Recent ones
look like this
: PyQt5-5.11.3-5.11.2_a-cp35.cp36.cp37.cp38-abi3-macosx_10_6_intel.whl

I noticed because it broke version parsing automation in my company. Now
that is not that important of course. But still there are questions

Can anyone shed some light on why wheels include 2 versions? Also Pip
cannot parse second version and if it's for humans the use still
unclear. Latter
is especially strange for names like in example above containing two patch
versions 5.11.3. And 5.11.2. Why not have only one.

Thanks.

Regards
Eduard
Florian Bruhin
2018-11-21 16:08:36 UTC
Permalink
Post by Eduard Babayan
Hello
Starting from pyqt5 version 5.7 wheels now include 2 versions. Recent ones
look like this
: PyQt5-5.11.3-5.11.2_a-cp35.cp36.cp37.cp38-abi3-macosx_10_6_intel.whl
I noticed because it broke version parsing automation in my company. Now
that is not that important of course. But still there are questions
Can anyone shed some light on why wheels include 2 versions? Also Pip
cannot parse second version and if it's for humans the use still
unclear. Latter
is especially strange for names like in example above containing two patch
versions 5.11.3. And 5.11.2. Why not have only one.
The first is the PyQt version, the second is the Qt version bundled in
it.

Florian
--
https://www.qutebrowser.org | ***@the-compiler.org (Mail/XMPP)
GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
I love long mails! | https://email.is-not-s.ms/
Phil Thompson
2018-11-24 11:39:35 UTC
Permalink
Hello
Starting from pyqt5 version 5.7 wheels now include 2 versions. Recent ones look like this : PyQt5-5.11.3-5.11.2_a-cp35.cp36.cp37.cp38-abi3-macosx_10_6_intel.whl
I noticed because it broke version parsing automation in my company. Now that is not that important of course. But still there are questions
Can anyone shed some light on why wheels include 2 versions? Also Pip cannot parse second version and if it's for humans the use still unclear. Latter is especially strange for names like in example above containing two patch versions 5.11.3. And 5.11.2. Why not have only one.
The '5.11.3' is the version number of PyQt.

The '5.11.2_a' is the build tag. pip should have no problem parsing it.

See...

https://www.python.org/dev/peps/pep-0427/#file-name-convention

For PyQt the build tag is made up of the version of Qt included in the wheel (ie. 5.11.2 in this case) optionally followed by an underscore and a letter (ie. '_a' in this case). The letter allows the release a new wheels to replace previous ones for the same PyQt and Qt versions.

Phil
_______________________________________________
PyQt mailing list ***@riverbankcomputing.com

Continue reading on narkive:
Loading...