On June 22, 2021 11:18:46 AM GMT+02:00, Henk-Jaap Wagenaar
<wagenaarhenkj...@gmail.com> wrote:
>On Tue, 22 Jun 2021 at 10:06, Petr Viktorin <encu...@gmail.com> wrote:
>
>> On 21. 06. 21 20:20, Guido van Rossum wrote:
>> > Okay, I think your evidence can then be discounted. Really, any app
>that
>> > relies on the publicly installed Python runs a serious risk of
>breaking
>> > when that Python gets updated, regardless of whether the ABI
>changes or
>> not.
>>
>> Unfortunately, this includes scripts for any extensible software
>> (Mayavi, GIMP, etc) -- even if Python is bundled with that software,
>> upgrading the software risks breaking the scripts.
>>
>>
>I'm confused by what you mean by this, or why it is a problem?
Not necessarily a problem, I just want to point out that there are situations
where you need to depend on Python managed by someone else.
>If I upgrade GIMP (and it vendors some version/variant of Python), it
>is
>not unreasonable that this would break a script that I have written in
>GIMPython? (GIMP should probably mention that it has changed its Python
>and
>how in the changelog/release notes)
>
>If I upgrade my OS, and I use the system Python, scripts I have written
>might break too.
>
>(Of course, GIMP is a placeholder here, I do not actually know what it
>does
>in terms of Python (vendoring), if at all.
GIMP itself doesn't, but it's sometimes distributed in flatpak/appimage with
its own bundled/pinned Python. (AFAIK it's usually Python 2.7, for a few
reasons; one of them being that upgrading would break scripts)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/ABK447E74NUXN6JUSKH6Y7WIQNWHQPTS/
Code of Conduct: http://python.org/psf/codeofconduct/
