Re: [Gimp-user] python-fu vs script-fu
- From: "ugajin talktalk net" <ugajin talktalk net>
- To: <ofnuts gmx com>, <gimp-user-list gnome org>
- Subject: Re: [Gimp-user] python-fu vs script-fu
- Date: Wed, 23 Mar 2016 10:22:10 +0000 (GMT)
Intersting idea, but running Python interactively before launching GIMP
does not seem to make a noticeable difference.
Thanks.
----Original Message----
From: ofnuts gmx com
Date: 22/03/2016 21:04
To: <gimp-user-list gnome org>
Subj: Re: [Gimp-user] python-fu vs script-fu
On 22/03/16 21:34, Kevin Cozens wrote:
On 16-03-22 03:04 PM, ugajin talktalk net wrote:
I don't see the difference to be about efficiency. There is
noticeable
lag when executing python-fu.
Script-Fu is always loaded in memory when GIMP starts. For Python
scripts the Python interpreter must be loaded before it can run the
script. The times it takes to load the Python interepreter would be
the lag you are talking about.
Possible. I don't experience such lags but then on a Linux system
there
is always a Python script running somewhere so the interpreter is
already loaded, and it's only a matter of initializing a new
instance.
But then on OSX I would expect the interpreter to be kept in the IO
buffers, so the lag would be noticeable only on the first execution.
A
good test would be to start an interactive python session before
starting Gimp, keep it open while Gimp runs and see if the lag
remains.
_______________________________________________
gimp-user-list mailing list
List address: gimp-user-list gnome org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives: https://mail.gnome.org/archives/gimp-user-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]