apidoc rootmodule registration should be automatic

Bug #180883 reported by Christophe Combelles
10
Affects Status Importance Assigned to Milestone
BlueBream
New
Undecided
Unassigned
Zope 3
Won't Fix
Undecided
Unassigned
zope.app.apidoc
New
Undecided
Unassigned

Bug Description

the root module that currently appear in the ++apidoc++ code browser are those registered in:
 zope/app/apidoc/codemodule/configure.zcml:

  <apidoc:rootModule module="BTrees" />
  <apidoc:rootModule module="RestrictedPython" />
  <apidoc:rootModule module="ThreadedAsync" />
  <apidoc:rootModule module="ZConfig" />
  <apidoc:rootModule module="ZODB" />
  <apidoc:rootModule module="persistent" />
  <apidoc:rootModule module="transaction" />
  <apidoc:rootModule module="zdaemon" />
  <apidoc:rootModule module="zope" />

First problem: ZODB rootmodule, ZConfig rootmodule, etc. should not be registered here.
zope.app.apidoc should not depend on there modules.

Second problem: other modules such as the instance or buildout development modules don't appear in the apidoc. They have to register themselves with an apidoc:rootModule directive.

---

First solution : remove these registrations from zope.app.apidoc, and move them into each module. This means that every module will depend on zope.app.apidoc, this is not acceptable.

Second better solution : let zope.app.apidoc discover itself all the root modules. How can we do that?

Revision history for this message
lukman (lukman-java89) wrote :

i want learn linux

Changed in zope3:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.