Bug#890200: PyQt5 package should provide an egg-info

[Bastian Germann]

I changed the package to include the files as described.

Bug#890200: PyQt5 package should provide an egg-info

[Bastian Germann]

There is no installed.txt file but a RECORD file which should not be
provided in this use case anyway.

>From the PEP: "The install command also provides an option to prevent
the RECORD file from being written and this option should be used when
creating system packages."

So there is no file list to be provided. The other dist-info files
(METADATA, INSTALLER) should be in python{,3}-pyqt5.

Bug#890200: PyQt5 package should provide an egg-info

[Ghislain Vaillant]

On Mon, 12 Feb 2018 23:35:14 -0500 Scott Kitterman  wrote:
> On Sunday, February 11, 2018 09:19:59 PM VA wrote:
> > Package: python-pyqt5
> > Version: 5.9.2+dfsg-1
> > 
> > Many Debian python packages include an egg-info folder, but python-
pyqt5
> > does not.
> 
> The PyQt5 upstream does not use standard Python tools for building
the 
> package.  As shipped by upstream, a source build of PyQt5:
> 
> python3 configure.py
> make
> sudo make install
> 
> does not install any egg information.  Only the upstream wheels
provide 
> anything.  They provide a PyQt5-5.10.dist-info directory which
appears to 
> perform a similar function.
> 
> This is probably not feasible in Debian as we split PyQt5 into a
number of 
> sub-packages to minimize the dependencies that get pulled in for
various 
> applications.  I'm not sure how to manage the egg-info for such a
case.
> 
> Scott K

The problem is that anything that explicitly depends on pyqt5 (as in
'pyqt5' being listed in install_requires) yields a DistributionNotFound
error. I am having this very issue with the recent release of spyder.

A solution is to remove the explicit dependency in order to trick the
setuptools metadata, but it is pretty ugly. Is there really no other
way?

Ghis

Bug#890200: PyQt5 package should provide an egg-info

[Scott Kitterman]

On Sunday, February 11, 2018 09:19:59 PM VA wrote:
> Package: python-pyqt5
> Version: 5.9.2+dfsg-1
> 
> Many Debian python packages include an egg-info folder, but python-pyqt5
> does not.

The PyQt5 upstream does not use standard Python tools for building the 
package.  As shipped by upstream, a source build of PyQt5:

python3 configure.py
make
sudo make install

does not install any egg information.  Only the upstream wheels provide 
anything.  They provide a PyQt5-5.10.dist-info directory which appears to 
perform a similar function.

This is probably not feasible in Debian as we split PyQt5 into a number of 
sub-packages to minimize the dependencies that get pulled in for various 
applications.  I'm not sure how to manage the egg-info for such a case.

Scott K

Bug#890200: PyQt5 package should provide an egg-info

[VA]

Package: python-pyqt5
Version: 5.9.2+dfsg-1

Many Debian python packages include an egg-info folder, but python-pyqt5 
does not.


For example, when python-requests is installed with apt:

% dpkg -L python-requests | grep egg-info
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/PKG-INFO
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/dependency_links.txt
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/not-zip-safe
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/requires.txt
/usr/lib/python2.7/dist-packages/requests-2.18.4.egg-info/top_level.txt
% dpkg -L python-pyqt5 | grep egg-info
%

When installing a pip package which requires a python dependency that is 
already installed with Debian packages, pip finds it and uses the 
Debian-installed package.
Since python-pyqt5 does not provide any, pip fails to find 'PyQt5' 
locally and so programs may fail to run even though PyQt5 is installed.