Benny Malengier skrev 2012-09-30 14:19:

All working again.
So if you do svn up, src directory will be changed to gramps. I hope that works good on all your PCs :-)

This is needed in order to not need to build gramps to test things (although, that is in itself not a bad thing, as like that your code directory remains clean, so no .pyc and friends)

To work with gramps after this change, just do in trunk:

1/ create a build directory with the code

 python build

2/ if you want to run from source, then create a in your repo. So something like:

cp build/lib.linux-x86_64-2.7/gramps/gen/ gramps/gen/

Note, on your computer, the directory in build will be different!

3/ to start gramps from the repo, in trunk directory:

 python Gramps

Note the capital G. I am wondering now if windows is already cap sensitive or not. Is it? Otherwise this Gramps will collide with the gramps dir, and we need another name
Windows is not cap sensitive, at least in Win 7 64 bits. Why not use (in windows) pythonw.exe

If you have installed GTK3 not globally, above will be rather:

 PYTHONPATH=/usr/local/lib/python2.7/site-packages/ python Gramps

or even
 PYTHONPATH=/usr/local/lib/python2.7/site-packages/ LD_LIBRARY_PATH=/usr/local/lib python Gramps

4/ to start gramps generally, only the correct PYTHONPATH must be passed. So if you installed in the build directory using python build, then you would need to make sure this is used, so to start gramps is then something like:

benny@dell:~$ PYTHONPATH=~/gramps/trunktest2/build/lib.linux-x86_64-2.7/ python ~/gramps/trunktest2/build/lib.linux-x86_64-2.7/gramps/

So executing gramps/ starts the Gramps application. Again, if you don't have installed GTK3 locally, it becomes something like:

benny@dell:~$ PYTHONPATH=/usr/local/lib/python2.7/site-packages/:~/gramps/trunktest2/build/lib.linux-x86_64-2.7/ python ~/gramps/trunktest2/build/lib.linux-x86_64-2.7/gramps/

Ok, this might seem complicated, but is actually standard python stuff.


2012/9/30 Benny Malengier <>
Big changes in trunk. But not finished, please don't commit yet.
I need to rename src into gramps, but am having problems, I'll only be able to do it in a couple of hours.

(svn mv src gramps did not work as expected locally, deleted everything but did not add everything again, will need to start from scratch for that).

If you have  patches in trunk, go to the __src__ dir and do there
svn diff > mypatch.diff

Then, make sure you remove trunk/gramps file, this was in svn ignore, it should no longer be in svn ignore.

Don't do svn up yet, wait for my go on the src to gramps name change. When that is ok, following will have changed:

First, src will be renamed as gramps. This is needed as we want to use gen as a separate module, and import from gui/cli this module without working relative, so we need import gramps.gen ...
To avoid needing build after every change, src must be renamed gramps, so that you can work from your branch without building.

src/ is renamed gramps/
This is needed as grampsapp puts gramps on the PYTHONPATH on execute as all python code, but then import gramps... is no longer defined as it referes to the gramps directory, not to So it is

To use gramps simply, trunk has a Gramps file, which sets things up, and uses a workaround for the time being. This workaround must be removed before release!

So to start gramps then from trunk do:

python Gramps

That's it!

Many changes still to do to have all imports correct, but they can be done as time permits.

Ok, have to go now, I'll do the rename from src to gramps later. If you do svn anyway already, you can make gramps work, but you need to create a soft link for gramps:

ln -s src gramps


Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:;258768047;13503038;j?

Gramps-devel mailing list