Bug#1008849: shiboken2 - Needs tighter dependency on python3
On Wed, Apr 13 2022, Nicholas D Steeves wrote:
> I understand, and agree that the issue is real, and that a rebuild is
> required. A binNMU is the most expedient solution ;-) Please read
> "What are binNMUs?" at the link provided above...
Yes, but I wouldn't call this "expedient", since ...
> Kurt, this is the point I'm wondering about, because it would be better
> if the transition tracker would alert us of outstanding issues rather
> than waiting for someone to report breakage. If this isn't feasible,
> could you document that fact in the source package?
... we're waiting for somebody to report the unavoidable breakage, since
shiboken2 enforces this through a minor version check (we're not hoping
it will work - it will just refuse to work).
That would be a "grave" bug report from that perspective, not too
dissimilar to any ABI breakage rendering downstream users _and_ packages
unusable until fixed.
> This might be by design. Kurt, do you know? There's also the question
> of if pyside2/shiboken2 is even py3.10-ready (I haven't tested yet).
Answering this for an hypothetical 3.11 transition, the answer would
similarly be "likely doesn't matter - it's worth attempting a build and
hope for the best, because the current version is broken".
> As a general principle, I worry that this would either reduce
> functionality and/or debugging, or introduce regression potential, so
> this is not a change I'm willing to make as a team member and not
> as one of the primary maintainers/uploaders of pyside2.
I understand this. And the documentation around this define is lacking
as well. Looking at the sources, it does seem to reduce the number of
exported methods, so it is fair to say we might have users that expect
the full API to be available and would break if used...
Reply to: