Hi Johannes,
If you haven't already noticed, I provided a better patch in the bug on bz.
I am pretty much struggling with adding a Python class 'testing.py' to a project. Though,
the problem doesn't seem to be my code, but the gbf-am code.
So, when I create a Python class and try to add it to the existing project, I
get the following debug output: (compiled anjuta with --enable-debug)
** (anjuta:17696): DEBUG: gbf-am-project.c:480>>>>>>>>>>>>>>>>>> root_uri:
file:///home/kenny/devel/anjuta/python-foobar, uri:
file:///home/kenny/devel/anjuta/python-foobar/src/testing.py, path:
/src/testing.py
Input XML to the script:
<?xml version="1.0"?>
<project root="/home/kenny/devel/anjuta/python-foobar"><add
type="source"><group id="/src/"><target id="teste.h:script"><source
uri="/src/testing.py"/></target></group></add></project>
** (anjuta:17696): DEBUG: gbf-am-project.c:2103 (spawn_script) Spawning script
** (anjuta:17696): DEBUG: gbf-am-project.c:1906 (spawn_write_child) wrote 207
bytes
Change set:
added source
/src/testing.py:script:file:///home/kenny/devel/anjuta/python-foobar/src/testing.py.c
added target /src/testing.py:script
You'll see that a ".c" is appended to the filename "testing.py", which was not
expected. I could reproduce that with a clean branch and C++/GObject classes,
so I reported a bug on that. [1]
[1] https://bugzilla.gnome.org/show_bug.cgi?id=637349
I could figure out how to edit the create Python class in a single buffer,
instead of two, and I don't know if I will be able to fix the other bug, in
the time that's left.
So this is also a call to update the GCI task accordingly, before it's too
late.
Regards,
Kenny
--
Encouraging respectful discussion with OpenRespect (http://www.openrespect.org)
Attachment:
pgpXavf1_opdl.pgp
Description: PGP signature