All,

With the change to gramps as a pure python module, we need a guideline on imports. You find it here:

http://www.gramps-project.org/wiki/index.php?title=Programming_guidelines#Imports

Current Gramps in trunk does not yet satisfy this, so I will be working following days to bring all pieces in line. Feel free to help me!
Once this is done, I will remove the sys.path.append trick which is now in Gramps.py, as that is the reason it works at the moment.

So, all imports should start with
import gramps......
or be relative imports.

No relative imports allowed between gen, cli, gui and plugins submodules.

The idea is, is then the following works:

benny@dell:~$ PYTHONPATH=~/gramps/trunk/build/lib.linux-x86_64-2.7/ python
Python 2.7.3 (default, Aug  1 2012, 05:14:39)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from gramps.gen.lib import Date
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/benny/gramps/trunk/build/lib.linux-x86_64-2.7/gramps/gen/lib/__init__.py", line 75, in <module>
    from markertype import MarkerType
  File "/home/benny/gramps/trunk/build/lib.linux-x86_64-2.7/gramps/gen/lib/markertype.py", line 34, in <module>
    from gen.ggettext import gettext as _
ImportError: No module named gen.ggettext
>>>

Clearly it doesn't work yet :-)

Benny