#3 Difficult to write a script using HappyDoc libraries

[Brad Chapman]

This isn't really a bug, but more of a feature request...

Right now it is pretty hard to write a script that will call happydoc_class, set some variables for a HappyDoc instance, and then call run. It would be very useful to be able to use HappyDoc as a library since then I can distribute scripts whose only requirements are that HappyDoc be installed on the PYTHONPATH.

The problem with calling happydoc_class from a script other than happydoc.py is that the pluginloader.py uses the location of happydoc.py script to determine where to find the plugins (via the APP_HOME_DIR constant). Could an alternate mechanism be used to find these plugins? It seems as if they wouldn't be very difficult to find if a standard location for the plugins was established (ie. os.curdir + pluginSetName).

Right now the workaround is to hack sys.path before importing HappyDoc, but this is pretty ugly.

Brad
chapmanb@arches.uga.edu

[Doug Hellmann]

Brad,

I agree that the HappyDoc class should be abstracted to allow other driver classes to be used to run it. For now this is a fairly low priority over some other features that I want to add, but I will add it to the list.

Doug

PS - I'm in Athens, too. Do you work on campus?

[Doug Hellmann]

Logged In: YES
user_id=34486

I believe the restructuring done as part of the 2.0 release should resolve most of these concerns.