ImportError: No module named 'PyQt5.sip'

[Phil Thompson]

Aah - I never build in that particular way, I always use pip to build 
the PyQt5.sip module.

To build from an unpacked source package...

     pip install .

To build from a local source package...

     pip install PyQt5_sip-12.7.2.tar.gz

To build from source from PyPI...

     pip install --no-binary :all: PyQt5-sip

I'll try and detect if 'python setup.py' is being used and either fix it 
or fail with an error message.

Phil

On 28/04/2020 13:39, Patrick Stinson wrote:
> Phil,
> 
> It seems to me that this is likely documented somewhere since it is a
> latest-version source build with generic options?
> 
> -Patrick
> 
>> On Apr 27, 2020, at 11:26 PM, Patrick Stinson <patrickkidd at gmail.com> 
>> wrote:
>> 
>> Now I am asking the same question as the OP. I built Python-3.8.4, 
>> sip-5.2.0, and PyQt5-5.14.2 on macOS and got the same error.
>> 
>> I built sip with “python setup.py install”
>> 
>> turin:vendor patrick$ python -c "import PyQt5.QtGui"
>> Traceback (most recent call last):
>>   File "<string>", line 1, in <module>
>> ModuleNotFoundError: No module named 'PyQt5.sip'
>> 
>> 
>> -Patrick
>> 
>>> On Apr 27, 2020, at 1:33 PM, Phil Thompson 
>>> <phil at riverbankcomputing.com> wrote:
>>> 
>>>> On 27/04/2020 22:19, Gabriele Bulfon wrote:
>>>> Great Phil, that's where I pulled sources for both of them.
>>>> I have built and packaged PyQt5-sip and PyQt5 from those sources,
>>>> after building and packaging sip5 and PyQt-builder.
>>>> 
>>>> Maybe there's something wrong in what I'm delivering to the system
>>>> with PyQt5-sip?
>>>> Here's a brief of the files delivered by my package, as in the 
>>>> package
>>>> definition file (pkg, solaris).
>>>> I derived this from the prototype area generated by the 
>>>> build/install
>>>> on the prototype install root.
>>>> I bet something is wrong with the sip.cpython-35m.so file...I still
>>>> don't understand how these cpython so files are looked up, but that 
>>>> is
>>>> what the build system created in the prototype area.
>>>> 
>>>> dir path=usr
>>>> dir path=usr/lib
>>>> dir path=usr/lib/python$(PYVER)
>>>> dir path=usr/lib/python$(PYVER)/vendor-packages
>>>> dir path=usr/lib/python$(PYVER)/vendor-packages/PyQt5
>>>> dir
>>>> path=usr/lib/python$(PYVER)/vendor-packages/PyQt5_sip-12.7.2-py$(PYVER).egg-info
>>>> file usr/lib/python$(PYVER)/vendor-packages/PyQt5/sip.cpython-35m.so
>>>> path=usr/lib/python$(PYVER)/vendor-packages/PyQt5/sip.cpython-35m.so
>>>> file
>>>> path=usr/lib/python$(PYVER)/vendor-packages/PyQt5_sip-12.7.2-py$(PYVER).egg-info/PKG-INFO
>>>> file
>>>> path=usr/lib/python$(PYVER)/vendor-packages/PyQt5_sip-12.7.2-py$(PYVER).egg-info/SOURCES.txt
>>>> file
>>>> path=usr/lib/python$(PYVER)/vendor-packages/PyQt5_sip-12.7.2-py$(PYVER).egg-info/dependency_links.txt
>>>> file
>>>> path=usr/lib/python$(PYVER)/vendor-packages/PyQt5_sip-12.7.2-py$(PYVER).egg-info/top_level.txt
>>> 
>>> I would expect to see .dist-info rather than .egg-info. Maybe your 
>>> setuptools is too old.
>>> 
>>> Phil
>>