Your message dated Tue, 30 Apr 2024 11:49:26 +0100
with message-id <[email protected]>
and subject line Re: Bug#1002662: pygobject: gi.importer.DynamicImporter should
implement PEP-0451
has caused the Debian Bug report #1002662,
regarding pygobject: gi.importer.DynamicImporter should implement PEP-0451
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1002662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002662
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pygobject
Version: 3.42.0-2
Severity: serious
X-Debbugs-CC: [email protected]
Tags: sid bookworm
User: [email protected]
Usertags: needs-update
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python2.10 to the supported Python
versions [0]. With a recent upload of python3-defaults the autopkgtest
of pygobject fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
pass fail
python3-defaults from testing 3.9.8-1
pygobject from testing 3.42.0-2
all others from testing from testing
I copied some of the output at the bottom of this report. It seems that
the test ran successfully but wrote a warning to stderr. By default
autopkgtest fails on that, which can be prevented by adding the
allow-stderr restriction. Please prevent the warning and/or add the
restriction.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists
what's new in Python2.10, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pygobject/17393447/log.gz
OK
<frozen importlib._bootstrap>:671: ImportWarning:
DynamicImporter.exec_module() not found; falling back to load_module()
test_glib_enum (__main__.TestGI)
GLib enum ... ok
test_glib_flag (__main__.TestGI)
GLib flag ... ok
test_method (__main__.TestGI)
GLib method call ... ok
----------------------------------------------------------------------
Ran 3 tests in 0.001s
[...]
autopkgtest [12:14:54]: test python3-all: - - - - - - - - - - results -
- - - - - - - - -
python3-all FAIL stderr: <frozen importlib._bootstrap>:671:
ImportWarning: DynamicImporter.exec_module() not found; falling back to
load_module()
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.46.0-1
On Sun, 26 Dec 2021 at 21:20:39 +0000, Simon McVittie wrote:
> Minimal reproducer:
>
> $ python3.10 -Wall
> >>> from gi.repository import GLib
>
> Good result: no warning; bad result; the same ImportWarning seen above.
Fixed upstream in 3.46.0 by commit 78eee1bb (and backported to 3.44.2,
but we never had that in Debian).
Confirmed fixed in trixie, using python3 (= python3.11) instead of
python3.10 for the reproducer.
smcv
--- End Message ---
