Unable to install PyQt6 using third party helpers (poetry, pipenv)

Eli Schwartz eschwartz at archlinux.org
Sun Jan 17 02:59:46 GMT 2021


On 1/16/21 9:14 PM, Ludovic Bellière wrote:
> Sorry, I wasn't very explicit. Poetry does install the dependencies, as
> they are present in the virtual environment, but fails to install PyQt6
> itself. Same goes for pipenv.

You're the one with the error message showing it's not properly 
installed while trying to install PyQt6. I don't know what to tell you.

The error message is explicitly telling you the dependency isn't there.

poetry did not install it, or did not install it early enough, or did 
not correctly install it, or something. However this came to be, it is 
not there, and poetry was responsible for ensuring it was there, and the 
lack of it caused PyQt6 to be unable to install.

> Poetry is a dependency manager, helps with dealing with multiple python
> versions or environments, can help building your wheels too. I'm fairly
> new to using poetry, so I invite you to read their own words:
> https://github.com/python-poetry/poetry/#why

venv / virtualenv is pretty good at dealing with multiple python 
versions or environments too -- so good in fact that poetry seems to 
import virtualenv and just use that, just like it runs pip to install 
things.

"their own words" from that README makes it sound like poetry wants to 
compete with *setuptools*, by replacing setup.py, even though most of 
the proliferation of files poetry is warning about is... not really an 
issue since there's no reason to use most of them? And quite frankly 
"less files due to adding many disparate things to *one* file" doesn't 
really sound like it reduces complexity.

FWIW -- pip has a new solver I'm told is quite nifty, so I'm not sure 
that's something poetry has as an advantage either.

But hey, if today's newest broken fad tool floats your boat, by all 
means use it.

>  From what I can observe, poetry uses a local repository to install
> packages in your virtual environment. pip freeze will show that the
> packages are installed from wheels instead of referencing their
> versions. But again, I'm just discovering the tool.

I'm not sure how this helps to figure out why poetry is broken w.r.t. 
dependency management of build-backend.requires, but I gotta say 
"implements a local cache of built wheels" isn't very impressive. PyPI 
has built wheels too, and pip caches them by default since 2015 (several 
years before poetry's first line of code ever got written), or builds 
wheels and caches those.

If this is (part of) your reason for using poetry, then it feels like 
you've been misled.

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20210116/71d89ed5/attachment.sig>


More information about the PyQt mailing list