[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] <bug>: still happening
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-bugs] <bug>: still happening |
Date: |
Wed, 19 Aug 2015 14:30:16 +0200 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Tue, Aug 18, 2015 at 02:09:15PM +0200, Marc Angermann wrote:
> client version: 1.5.7.rc1
>
> user comment : still happening
In fact, no.
While initial logging shows that gnumed.py of 1.5.7.rc1 is run:
> 2015-08-18 14:07:17 INFO gm.launcher (gnumed.py::log_startup_info()
> #277): GNUmed client version [1.5.7.rc1] on branch [1.5]
apparently from
C:\Users\marc\Downloads\gnumed-client.1.5.7.rc1\client\
However, Python modules are imported from the systemwide installation
> 2015-08-18 14:07:17 INFO gm.logging
> (C:\Python27\lib\site-packages\Gnumed\pycommon\gmLog2.py::__setup_logging()
> #270): log file is
> <C:\Users\marc\Downloads\gnumed-client.1.5.7.rc1\client\gm-from-vcs.log>
at
C:\Python27\lib\site-packages\Gnumed\pycommon\
rather than from
C:\Users\marc\Downloads\gnumed-client.1.5.7.rc1\Gnumed\pycommon\
There's two reasons why this can happen. Either PYTHONPATH
(and thusly sys.path) does not know about
C:\Users\marc\Downloads\gnumed-client.1.5.7.rc1\Gnumed\
or
C:\Users\marc\Downloads\gnumed-client.1.5.7.rc1\Gnumed\
doesn't exist -- it is a _link_ to
C:\Users\marc\Downloads\gnumed-client.1.5.7.rc1\client\
which gets created by gnumed.py when run with --local-import.
Now, sys.path isn't logged (until now) but $PYTHONPATH is:
> 2015-08-18 14:07:18 INFO gm.launcher (gnumed.py::log_startup_info()
> #289): ${PYTHONPATH}: ..\;
and $PYTHONPATH is what sys.path is initially set to (plus a
few system-internal directories).
This begs the questions:
Exactly how do you start GNUmed ?
Does the symlink .../Gnumed/ -> .../client/ exist ?
What is the current working directory when you start GNUmed ?
I have now added logging of CWD.
I suggest adding --local-import inside gm-from-vcs.bat and
trying again because the outcome of all of the above is that
the tarball runs with the old Python modules installed
systemwide which explains why the old bug still shows.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346