Bug#1001368: pygobject: autopkgtest needs update for python3.10: ImportWarning: DynamicImporter.exec_module() not found
Simon McVittie
smcv at debian.org
Sun Dec 26 21:20:39 GMT 2021
Control: clone -1 -2
Control: tags -1 + pending
Control: retitle -2 pygobject: gi.importer.DynamicImporter should implement PEP-0451
Control: severity -2 normal
Control: user debian-ci at lists.debian.org
Control: usertags -2 - needs-update
On Thu, 09 Dec 2021 at 09:55:49 +0100, Paul Gevers wrote:
> python3-all FAIL stderr: <frozen importlib._bootstrap>:671:
> ImportWarning: DynamicImporter.exec_module() not found; falling back to
> load_module()
Minimal reproducer:
$ python3.10 -Wall
>>> from gi.repository import GLib
Good result: no warning; bad result; the same ImportWarning seen above.
For now, I'm going to make the ImportWarning stop failing the test, by
adding the allow-stderr restriction.
This solves the autopkgtest failure, which is RC, but does not solve the
underlying non-RC bug: pygobject should implement the new PEP-0451 methods.
I've cloned "pygobject: gi.importer.DynamicImporter should implement
PEP-0451" to represent the underlying bug. This might become RC when we
go to python3.11 or python3.12 or something, if it is not solved upstream
before then, but is not RC *yet*.
I am not sufficiently familiar with the finer points of the Python import
mechanism to be able to reimplement pygobject's import hooks for PEP-0451.
smcv
More information about the pkg-gnome-maintainers
mailing list