[Debian-med-packaging] Bug#516037: gnumed-client: hard-codes the location to python modules

Karsten Hilbert Karsten.Hilbert at gmx.net
Thu Feb 19 08:40:44 UTC 2009

On Thu, Feb 19, 2009 at 09:31:52AM +0100, RKI Andreas wrote:

>> The "trivial" seems to come about by the misbelief that our
>> module imports somehow use GNUMEDDIR which they do not.
>> That's only used to access gnumed.py, nothing else.
>> gnumed(.sh) is there exactly to *be* a shell wrapper around
>> gnumed.py to allow the user to run additional shell scripts
>> before launching GNUmed. It doesn't make any sense to
>> convert it to Python.
> So the fix for the bug is really simple: Install the Python
> modules at *any* place which the Pathon policy suggests and
> adapt the shell script to this place, right?

Well, no, the GNUmed code expects to be able to do the
standard thing:

	from Gnumed.pycommon import ...

without prior sys.path/PYTHONPATH manipulation for which the
GNUmed modules need to be in a module directory accessible
systemwide, say site-packages/Gnumed/  .

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

More information about the Debian-med-packaging mailing list