#Pipenv install pyqt5 install
#Pipenv install pyqt5 full

#Pipenv install pyqt5 install

My best analysis at this point suggests two issues: vext.pyqt5 may not be properly declaring dependencies (hence error when not installed using -sequential), and it seems to be doing something that requires the environment to be active in order to install correctly.ДЄt this point I'm not sure if this merits its own issue. Error on install when pipenv install vext.pyqt5 is run from main shell (outside venv subshell) after environment is initialized.

0.7.0 installs and functions after pipenv uninstall vext.pyqt5 & pipenv install vext.pyqt5 - but only when these commands are run from within the pipenv shell.

0.7.0 apparently installs ok via pipenv install -sequential with the package late in my dependency spec.

0.7.0 installs OK from within pipenv shell without PIP_NO_BINARY (and works) but does not work (and errors) when installed via pipenv install.

0.5.21 still errors on pipenv install even with `PIP_NO_BINARY=vext.pyqt5.

#Pipenv install pyqt5 full

I didn't want to paste the full error message above because it's long, but here's the relevant part from pipenv install vext.pyqt5:Д®DIT: Original comment preserved below, but I no longer think the vext.pyqt5 issue is related to installing with -no-binary vs. I recognize that in this case it may be addressable by correcting some issue in the vext.pyqt5 package, but I still think it's another argument for adding this kind of argument to the Pipfile spec - and I will add this comment to an issue on the Pipfile repo if/when that happens.Д®dit: seems that the vext author is aware of this as a (non)-problem since 2016 - vext-python/vext#37 - maybe I should open/reopen the issue there since it now is an issue for pipenv initialization? This can be verified by, e.g., import pyqtgraph in my context. Interestingly: if I leave this out of my Pipfile initially, and then after installing the rest of the environment I use pipenv install vext.pyqt5 to install the package, that command reports a (test?) error but I get an entry added to my Pipfile and a functional package. I get a warning about the failed package installation, a notice that it's retrying, this appears to succeed (the command finishes w/o error), and the package is listed as installed but non-functional. I have not had any success with this in my Pipfile when I try to initially create an environment using pipenv install. I've tried things along the line of this: Unfortunately I cannot find any way to specify this package in my Pipfile and have it get installed when I spin up an environment.

I have confirmed that using this variant of the install command works (on previous pip versions it would apparently have been -no-use-wheel). Pip install -no-binary vext.pyqt5 vext.pyqt5 For some reason this package does not play nice when installed from wheel - and I agree this is probably a bug in the package that should be addresssed - so in a classic venv workflow you would install with: The cleanest way I have found to use system-installed pyqt(5) in a venv is to install vext.pyqt5, which basically installs shims to use the system copy of pyqt5 in the virtual environment. I'm not sure this is the same issue but I think it is, so here's another (possible) use case that doesn't seem to be supported with current syntax I can find documented: