[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] Re: API automatic updating probelm (was Re: patient searc
From: |
Karsten Hilbert |
Subject: |
[Gnumed-devel] Re: API automatic updating probelm (was Re: patient searches) |
Date: |
Tue, 15 Feb 2005 11:02:00 +0100 |
User-agent: |
Mutt/1.3.22.1i |
> >That needs updating. The automatic updating still chokes on
> >wxPython to which no one apparently has an answer.
>
> If the API is worth updating manually (until it can run
> automatically) what frequency would you suggest it be done manually?
> Once a week?
Once a week.
> Once a month? What is the procedure to update it
> manually and what permissions (and any locally installed software)
> are required to do so?
Run the shell script to generate the epydoc docs locally under
X with DISPLAY set.
> Is the above a different problem from an Epydoc problem noted
> previously 9which we already have on the wiki):
>
> does not list files under wxpython/ as at July 12, 2004. Epydoc may
> not descend to subdirs if those are not part of a module. The easiest
> fix would be to have single documentation trees for wxpython,
> wxpython/gui and wxpython/patient. One nice side effect is that one
> can clearly see where documentation is missing or where the interface
> is not very clearly structured.
That "problem" is actually totally bogus.
Epydoc tries to import all files in the tree it is told to
document. If those files import wx on their own behalf that
will fail if X isn't running and accessible. If that fails
importing the file by epydoc will fail. At which point epydoc
decides to not try any further (stupid behaviour that, IMO).
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346