Hi Yuri and Kurt, Kurt, would you please read the following discussion, and comment if it's possible to generate a tighter Python dependency at build time? Yuri D'Elia <wavexx@thregr.org> writes: > On Tue, Apr 12 2022, Nicholas D Steeves wrote: >>> This also requires that shiboken2 should be currently rebuilt. >>> >> >> Agreed. >> >>> Either the python3 dependency should be tightened, or FORCE_LIMITED_API >>> should be used. >> >> These are not the only available options. Are you aware of binNMUs? >> https://wiki.debian.org/binNMU > > I'm using it for development, and not being able to work if the minor > version changes is a bigger problem than it sounds: I cannot rebuild > third-party software which is using shiboken/pyside unless I completely > rebuild pyside in parallel. > 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... > I remember I already had this issue with the 3.9 transition. > Yes, this is totally normal during transitions, and this is why transitions are needed. You can also see proof of past binNMUs here: https://snapshot.debian.org/binary/libshiboken2-py3-5.15/ Those "+b" versions are binNMUs. > IMHO if shiboken2 is tied to the minor version, it should depend on the > minor version as well so that the whole pyside/shiboken2 so that > transitions and downstream dependencies will also be handled as part of > the transitions? > > For example, the current situation is probably breaking packages which > are currently build with shiboken. > 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? > This makes shiboken2 completely useless if you have more than a one > minor version of python installed (for example during transition > periods). shiboken2 will work only for _one_ minor version. > 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). > I actually don't use shiboken2 _directly_ myself, but is there any real > drawback to build with FORCE_LIMITED_API ? 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 can however test py3.10 compatibility and request a binNMU. Best, Nicholas
Attachment:
signature.asc
Description: PGP signature