Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.os.linux.misc,comp.graphics.misc,nz.comp
Subject: Python 3 For GIMP 2
Date: Tue, 26 Mar 2024 22:35:39 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 16
Message-ID: <utvijr$2cr93$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 26 Mar 2024 22:35:39 +0100 (CET)
Injection-Info: dont-email.me; posting-host="90291ef565d63fc237f28fce5133db79";
	logging-data="2518307"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18/5ORxOLNBvqm78npXKoS0"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:nBrPmTpeQF/GQqK4wzFGcSWphKU=
Bytes: 1775

As you may know, GIMP 3 is taking a while to appear. In the meantime,
the Python API in GIMP 2 is built on obsolete Python 2, which many
distros have dropped. This leaves their standard GIMP 2 packages
without Python support.

However, there is another solution. It turns out the core of GIMP has
no dependency on Python at all, so it is possible to create
alternative wrappers around the shareable libraries that are used by
GIMP plugins (libgimp-2.0.s0.0 etc).

I have done this using the ctypes library that comes with Python 3, to
create the Pylibgimp2 project <https://gitlab.com/ldo/pylibgimp2>. So
far, the API wrapper has been good enough to port some simple (less
than 100 lines each) GIMP plugins that I wrote many years ago. It’s
not complete, by any means. But let me know if this sort of thing is
worth persevering with, and maybe I’ll do some more work on it. ;)