Benny Malengier skrev 2012-09-30 14:19:
Windows is not cap sensitive, at least in Win 7 64 bits. Why not use
(in windows) pythonw.exe Gramps.py?
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 setup.py build
2/ if you want to run from source, then create a const.py in your
repo. So something like:
Note, on your computer, the directory in build will be different!
3/ to start gramps from the repo, in trunk directory:
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
If you have installed GTK3 not globally, above will be
PYTHONPATH=/usr/local/lib/python2.7/site-packages/ python Gramps
4/ to start gramps generally, only the correct PYTHONPATH must be
passed. So if you installed in the build directory using python
setup.py build, then you would need to make sure this is used, so
to start gramps is then something like:
So executing gramps/grampsapp.py starts the Gramps application.
Again, if you don't have installed GTK3 locally, it becomes
Ok, this might seem complicated, but is actually standard python
2012/9/30 Benny Malengier <email@example.com>
Big changes in trunk. But not finished, please don't commit
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
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
To avoid needing setup.py build after every change, src must
be renamed gramps, so that you can work from your branch
src/gramps.py is renamed gramps/grampsapp.py
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
gramps.py. So grampsapp.py 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:
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:
Gramps-devel mailing list