[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] error in create gnumed db
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] error in create gnumed db |
Date: |
Wed, 14 Jul 2004 07:37:59 +0200 |
User-agent: |
Mutt/1.3.22.1i |
> Still trying to get gnumed up again - switched temporarily back to
> debian box as at least the egenix stuff works there.
>
> started with virgin db and downloaded cvs:
>
> dropdb gnumed
> createdb gnumed
You don't need any of that if you use Ian's installer frontend
or the bootstrap installer directly.
> then ran ian's install script and get following error
>
> Traceback (most recent call last):
> File "bootstrap-gm_db_system.py", line 70, in ?
> from Gnumed.pycommon import gmLog
> ImportError: No module named Gnumed.pycommon
When we say
from Gnumed.pycommon import something
this means
import $PYTHONLIB/site-packages/Gnumed/pycommon/something.py
So, you must have a Gnumed/* hierarchy under site-packages/
*or* you can make a Gnumed directory anywhere and add it to
PYTHONPATH (not $PYTHONLIB !).
Two ways to do that:
a) create a link $PYTHONLIB/site-packages/Gnumed to
gnumed/client of your CVS tree,
later this link would be replaced with an installed copy of
that part of the CVS tree
b) add gnumed/client/ to $PYTHONPATH, this is what the shell
scripts in the CVS tree do (eg the gnumed wrappers and the
redo-*.sh wrappers), Ian could just add that to his
installer
Eventually, an installer would copy the necessary stuff to
site-packages/Gnumed/.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Re: [Gnumed-devel] error in create gnumed db, Jim Busser, 2004/07/13
Re: [Gnumed-devel] error in create gnumed db,
Karsten Hilbert <=
Message not available