Thank you for raising this Axel. Using /usr/bin/env python3 works for me since the responsibility to bump is not on user anymore. Which brings me to my concern with the annoucement is that we move responsibility from a "system" to maintainers or some mass bump in devel:python (again maintainer(s)). Bumping shebang sounds like too much work with every system-python change (I'm aware of the macro which covers it, if maintainer didn't do the job). I suppose customer would not have to deal with it as changes on SLES / ALP would be not so often. Just my thoughts Lubos On Tue, 2023-10-10 at 13:13 +0200, Axel Braun wrote:
Hi Daniel,
Am Dienstag, 10. Oktober 2023, 08:22:54 CEST schrieb Daniel Garcia via openSUSE Factory:
Right now /usr/bin/python3 is a link provided by the current system python package that today is python311, in Factory. Any package that provides a python script with the shebang #!/usr/bin/python3 will have the requirement on /usr/bin/python3.
Does it catch the /usr/bin/env python[3] as well?
Cheers Axel