Re: [Gnumed-devel] error in create gnumed db - errors

[Karsten Hilbert]

On Wed, Jul 14, 2004 at 10:33:01AM +1000, Richard wrote:
> 
> 1) Did address@hidden:~/gnumed/gnumed$ ln -s client Gnumed
> 2) ran:
> address@hidden:~/gnumed/gnumed/server/bootstrap$ python ian_bootgnumed.py
> log file is [/home/richard/.ian_bootgnumed/ian_bootgnumed.log]

>     from Gnumed.pycommon import gmLog, gmPG
> ImportError: No module named Gnumed.pycommon
It still can't find the Gnumed.pycommon package. That means it
is neither referenced from PYTHONPATH nor directly from
site-packages.

> > Go to gnumed/gnumed, then create a symbolic link like so:
> > ln -s client Gnumed
This does not suffice. You either have to

- create the in-tree link AND add to PYTHONPATH (this is what
  my in-tree shell scripts do)

OR

- create a link directly from site-packages (you need to be
  root) to the CVS tree

(or both, in which case Python will use whatever comes first)

The first can be done in Ian's shell script, too. However, I
don't understand the added value you are offering here ?

No amount of layering removes the need for teaching Python
where to find GnuMed modules whether on an end-user install
machine or a developers machine.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346