On 9/9/06, Baiju M [EMAIL PROTECTED] wrote:
On 9/8/06, Michael Haubenwallner [EMAIL PROTECTED] wrote:
Michael Haubenwallner wrote:
Anyway, using the right paths i get back to where i initially started:
the package information is not displayed for several packages
pydoc displays package
Michael Haubenwallner wrote:
i have a small problem using pydoc to look at the Zope3 source, namely
zope.proxy and modules where zope.proxy is included:
running pydoc2.4 zope.proxy or pydoc2.4 zope.proxy._zope_proxy_proxy
from the shell yields
problem in zope.component - ImportError:
Stephan Richter wrote:
On Friday 08 September 2006 03:13, Michael Haubenwallner wrote:
i have a small problem using pydoc to look at the Zope3 source, namely
zope.proxy and modules where zope.proxy is included:
Why would you use pydoc? Any conventional documentation tools are useless in
Zope
On Friday 08 September 2006 09:03, Philipp von Weitershausen wrote:
Of course, that'd take a lot of resources (which we aren't likely to
have) and it always sems a good idea to at least *allow* third party
software to work with Zope.
The API in apidoc is developed in a way that it supports
Michael Haubenwallner wrote:
Anyway, using the right paths i get back to where i initially started:
the package information is not displayed for several packages
pydoc displays package information on zope.proxy, zope.component,
zope.interface for example like this:
-
Help on package
Stephan Richter wrote:
On Friday 08 September 2006 09:03, Philipp von Weitershausen wrote:
Of course, that'd take a lot of resources (which we aren't likely to
have) and it always sems a good idea to at least *allow* third party
software to work with Zope.
The API in apidoc is developed in a
