Hi.
Did someone try to run the python plug-in mentioned in the subject?
(seearakne new stich plug-in
I put also gimpfu2.py in the same folder where I put the arakne script (otherwise the plug-in does not even show up).
My steps are:
1-load the background image
2-load as a layer the overimposing image
3-define the base path (between the two eyes, as in the example)
4-named the path "base"
5-select new path
6-created a second path on the overimposing layer (again, between the two eyes)
7-named the second path "over"
8-called the script
but I do not see the plug-in window as in the example, but a kind of a text window (look like an error message but it does not show up in the error window)
if I hit OK, the plug-in run for a while but produces nothing.
I guess I need help from Ofnuts, the magician of "paths"...
Practically, what the script is assumed to do is: rotate and scale the overimposing layer so that the second path override the first (base) path.

The exact-aligner script does the same thing but in a better way:

1) uses one path instead of two

2) the scaling and orientation are done in one single transform operation, so there is only one occurrence of pixel interpolation instead of two (less interpolation: cleaner result)

Yes, you are right, Ofnuts!
I have that .scm and it works perfectly.
I was just curious about this new .py

Apart from the fact that exact-aligner.scm works perfectly, did someone anyhow test the new arakne gimp-stitch3.py (which include reference to gimpfu2)?
I was unable to have it run (just for curiosity and comparison...)

Of course, it tries to import gimpfu2 and doesn't find it. So either you change that yourself, or you convince the author to make a bi-modal script (tries to import gimpfu2, and if that fails, falls back to gimpfu).

Ofnuts, as I said in my first post
"I put also gimpfu2.py in the same folder where I put the arakne script (otherwise the plug-in does not even show up)."
So, it finds gimpfu2, shows up but does not show (my fault?) the parameters window as expected (as seen in the example)

addendum:
because it seems that the plug-in does not make use of the possibilities of gimpfu2, i modified it to include gimpfu instead of gimpfu2 and it behaves as expected.
So, either including gimpfu2 is not sufficient or something other is wrong. Peace...