RE:pyqt5 and entrypoint
On February 2, 2020 9:58:45 PM UTC, PICCA Frederic-Emmanuel
wrote:
>Hello
>
>on unstable it works but on buster (and we need to make it work for
>buster)
>we have this message
>
>Python 3.7.3 (default, Apr 3 2019, 05:39:12)
>[GCC 8.3.0] on linux
>Type "help", "copyright", "credits" or "license" for more information.
import pkg_resources
pkg_resources.get_distribution('PyQt5')
>Traceback (most recent call last):
> File "", line 1, in
>File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
>481, in get_distribution
>dist = get_provider(dist)
>File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
>357, in get_provider
> return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
>File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
>900, in require
>needed = self.resolve(parse_requirements(requirements))
>File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
>786, in resolve
>raise DistributionNotFound(req, requirers)
>pkg_resources.DistributionNotFound: The 'PyQt5' distribution was not
>found and is required by the application
Since you know that the dependency is satisfied due to your package
dependencies in debian/control, you should be able to patch away the requires
PyQt5 in setup.py and it'll work fine.
Scott K
Bug#950516: file: please backport 5.38 to stable for removal of python2
Package: file Severity: normal Control: block 936952 by -1 X-Debbugs-CC: debian-python@lists.debian.org Hi, In stable, the file utility (5.34) does not recognize byte-compiled python3 binaries, even though they were generated by the default python3 for that release (3.7.3). The version currently in unstable (5.38) should work. Will you please provide a backport or a security upload? If the first point is not enough, Lintian depends on the identification via 'file' to provide the tag 'source-contains-prebuilt-python-object'. Without it, Lintian cannot test the tag on stable and would likely drop it. Lintian has to stop using python2, which is being removed from Debian, to generate test binaries and must instead rely on python3 even on stable. Lintian cannot resort to python2 on stable alone, because python3 stores byte-compiled binaries in a different location (__pycache__). Kind regards Felix Lechner
RE:pyqt5 and entrypoint
Hello
on unstable it works but on buster (and we need to make it work for buster)
we have this message
Python 3.7.3 (default, Apr 3 2019, 05:39:12)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pkg_resources
>>> pkg_resources.get_distribution('PyQt5')
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 481, in
get_distribution
dist = get_provider(dist)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 357, in
get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'PyQt5' distribution was not found and
is required by the application
Re: pyqt5 and entrypoint
Hi,
On Sun, Feb 02, 2020 at 08:21:51PM +, PICCA Frederic-Emmanuel wrote:
> Hello,
>
> We are working on the next pyfai package.
>
> This new version use entry_points like this
> [...]
>
> But once installed, we can not start the gui application.
> [...]
>
> pkg_resources.DistributionNotFound: The 'PyQt5' distribution was not
> found and is required by the application
>
> indeed python3-pyqt5 was installed
Please make sure you have python3-pyqt5 ≥ 5.12+dfsg-1.
If that is the case and you are still getting an error, please check
the output of the following commands in the Python console:
>>> import pkg_resources
>>> pkg_resources.get_distribution('PyQt5')
For me it prints “PyQt5 5.14.1 (/usr/lib/python3/dist-packages)”.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
pyqt5 and entrypoint
Hello,
We are working on the next pyfai package.
This new version use entry_points like this
gui_requires = ['PyQt5', 'h5py', 'hdf5plugin', 'PyOpenGL']
opencl_requires = ['pyopencl']
extras_require = {
'calib2': gui_requires, # Keep compatibility
'gui': gui_requires,
'opencl': opencl_requires,
'full': gui_requires + opencl_requires,
}
console_scripts = [
'check_calib = pyFAI.app.check_calib:main',
'detector2nexus = pyFAI.app.detector2nexus:main',
'diff_map = pyFAI.app.diff_map:main',
'diff_tomo = pyFAI.app.diff_tomo:main',
'eiger-mask = pyFAI.app.eiger_mask:main',
'MX-calibrate = pyFAI.app.mx_calibrate:main',
'pyFAI-average = pyFAI.app.average:main',
'pyFAI-benchmark = pyFAI.app.benchmark:main',
'pyFAI-calib = pyFAI.app.calib:main',
'pyFAI-calib2 = pyFAI.app.calib2:main [gui]',
'pyFAI-drawmask = pyFAI.app.drawmask:main',
'pyFAI-diffmap = pyFAI.app.diff_map:main',
'pyFAI-integrate = pyFAI.app.integrate:main',
'pyFAI-recalib = pyFAI.app.recalib:main',
'pyFAI-saxs = pyFAI.app.saxs:main',
'pyFAI-waxs = pyFAI.app.waxs:main',
]
entry_points = {
'console_scripts': console_scripts,
# 'gui_scripts': [],
}
But once installed, we can not start the gui application.
jerome@patagonia:~/workspace/hdf5plugin$ pyFAI-calib2
Traceback (most recent call last):
File "/usr/bin/pyFAI-calib2", line 11, in
load_entry_point('pyFAI==0.19.0', 'console_scripts', 'pyFAI-calib2')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2793,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2410,
in load
self.require(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2433,
in require
items = working_set.resolve(reqs, env, installer, extras=self.extras)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'PyQt5' distribution was not
found and is required by the application
indeed python3-pyqt5 was installed
so Is it a bug in the pyqt5 package, or is there a way to fix this in Debian.
thanks for your help
Frederic
Re: Bug#949187: transition: python3.8
On Sun, Feb 02, 2020 at 06:12:08PM +0100, Rene Engelhard wrote: > Hi, > > On Sun, Feb 02, 2020 at 06:07:29PM +0100, Matthias Klose wrote: > > > e.g. fontforge is still red in > > > https://release.debian.org/transitions/html/python3.8.html. > > > > > > That means that a rebuild of stuff using fontforge in the build will > > > just FTBFS since it will be called with python3.8 and that has no module > > > for 3.8 (yet). > > > > > > (Seen in a python-3.8-as-default testbuild for libreoffice some time > > > ago.) > > > > you are wrong. fontforge just builds for the default python version. > > OK, maybe. But that also means that when python3.8 is default and > fontforge isn't yet rebuilt for python3.8-as-default but some package > from my list is rebuilt the same problem happens. OK; inded it seems to just work. Maybe I even misremembered an it was graphite2 and python3-fonttools. (Reused the chroot for multiple tests.) But I *had* a module import failure when I tried some months ago. Regards, Rene
Re: Bug#949187: transition: python3.8
Hi, On Sun, Feb 02, 2020 at 06:07:29PM +0100, Matthias Klose wrote: > > e.g. fontforge is still red in > > https://release.debian.org/transitions/html/python3.8.html. > > > > That means that a rebuild of stuff using fontforge in the build will > > just FTBFS since it will be called with python3.8 and that has no module > > for 3.8 (yet). > > > > (Seen in a python-3.8-as-default testbuild for libreoffice some time > > ago.) > > you are wrong. fontforge just builds for the default python version. OK, maybe. But that also means that when python3.8 is default and fontforge isn't yet rebuilt for python3.8-as-default but some package from my list is rebuilt the same problem happens. Then fontforge (which is not in the list below!) needs to be rebuilt before https://release.debian.org/transitions/html/python3.8-default.html is worked on. Didn't see it there so wanted to go sure. Regards, Rene
Re: Bug#949187: transition: python3.8
On Sun, Feb 02, 2020 at 05:53:37PM +0100, Rene Engelhard wrote: > On Sun, Feb 02, 2020 at 09:35:04AM +0100, Matthias Klose wrote: > > > On 17-01-2020 23:28, Matthias Klose wrote: > > >> Please add a transition tracker to switch the python3 default to 3.8. > > >> It's not > > >> yet ready, however it would be good to see affected packages. Please > > >> copy it > > >> from the 3.7 defaults change if possible. > > > > > > Tracker is in place. Please remove the moreinfo tag when you're ready. > > > > I think this is now in shape to be started. bug reports have been filed for > > I don't think so. > > e.g. fontforge is still red in > https://release.debian.org/transitions/html/python3.8.html. > > That means that a rebuild of stuff using fontforge in the build will > just FTBFS since it will be called with python3.8 and that has no module > for 3.8 (yet). $ grep-dctrl fontforge -FBuild-Depends /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources | grep-dctrl python3 -FBuild-Depends -sPackage Package: diffoscope Package: fonts-allerta Package: fonts-courier-prime Package: fonts-gotico-antiqua Package: fonts-junicode Package: fonts-karmilla Package: fonts-le-murmure Package: fonts-rit-sundar Package: fonts-smc-anjalioldlipi Package: fonts-smc-dyuthi Package: fonts-smc-karumbi Package: fonts-smc-keraleeyam Package: fonts-smc-meera Package: fonts-smc-rachana Package: fonts-smc-raghumalayalamsans Package: fonts-smc-uroob Package: fonts-solide-mirage Package: libreoffice Package: mftrace Package: searx Regards, Rene
Re: Bug#949187: transition: python3.8
On 2/2/20 5:53 PM, Rene Engelhard wrote: > On Sun, Feb 02, 2020 at 09:35:04AM +0100, Matthias Klose wrote: >>> On 17-01-2020 23:28, Matthias Klose wrote: Please add a transition tracker to switch the python3 default to 3.8. It's not yet ready, however it would be good to see affected packages. Please copy it from the 3.7 defaults change if possible. >>> >>> Tracker is in place. Please remove the moreinfo tag when you're ready. >> >> I think this is now in shape to be started. bug reports have been filed for > > I don't think so. > > e.g. fontforge is still red in > https://release.debian.org/transitions/html/python3.8.html. > > That means that a rebuild of stuff using fontforge in the build will > just FTBFS since it will be called with python3.8 and that has no module > for 3.8 (yet). > > (Seen in a python-3.8-as-default testbuild for libreoffice some time > ago.) you are wrong. fontforge just builds for the default python version.
Re: Bug#949187: transition: python3.8
On Sun, Feb 02, 2020 at 09:35:04AM +0100, Matthias Klose wrote: > > On 17-01-2020 23:28, Matthias Klose wrote: > >> Please add a transition tracker to switch the python3 default to 3.8. > >> It's not > >> yet ready, however it would be good to see affected packages. Please copy > >> it > >> from the 3.7 defaults change if possible. > > > > Tracker is in place. Please remove the moreinfo tag when you're ready. > > I think this is now in shape to be started. bug reports have been filed for I don't think so. e.g. fontforge is still red in https://release.debian.org/transitions/html/python3.8.html. That means that a rebuild of stuff using fontforge in the build will just FTBFS since it will be called with python3.8 and that has no module for 3.8 (yet). (Seen in a python-3.8-as-default testbuild for libreoffice some time ago.) Regards, Rene
Re: Request to join DPMT
Hi Christoph (2020.01.30_20:31:09_+) > I'd like to join DPMT to maintain my Python modules mercurial-keyring and > mercurial-keyring-utils. > > I've read and accept policy.rst. > > My salsa login is: eraserix-guest Welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Bug#949187: transition: python3.8
Control: tags -1 - moreinfo On 1/18/20 9:30 PM, Paul Gevers wrote: > Control: tags -1 moreinfo > > Hi Matthias, > > On 17-01-2020 23:28, Matthias Klose wrote: >> Please add a transition tracker to switch the python3 default to 3.8. It's >> not >> yet ready, however it would be good to see affected packages. Please copy it >> from the 3.7 defaults change if possible. > > Tracker is in place. Please remove the moreinfo tag when you're ready. I think this is now in shape to be started. bug reports have been filed for issues with 3.8 in [1], and there may be some which are missing the proper tagging. I also filed bug reports for a dozen missing dh-python build dependencies. I would prefer a transition slot with less activity with transitions in the science area, like opencv, openmpi, gnuradio, ros*, and others which only build extensions for the default python3 version. Matthias [1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.8;users=debian-python@lists.debian.org
