Re: [HappyDoc-discuss] Generating documentation from non .py files?

[Doug H. <do...@he...>]

No, you haven't missed something simple; this should work.  I assume your cgi 
file is in Python, right?  That should be allowed, but currently isn't.  The 
docset assumes that only files ending in .py are Python files.  Other 
extensions should be allowed, for cases like this.  There is a policy 
question, however, about whether to always allow .cgi files or to only allow 
them if they are specified on the command line.  

Perhaps the simplest thing to do is just let the user specify additional 
filename extensions as options.  That moves the decision from us to the user.

I'd appreciate it if you would post this as a feature request.  There are a 
few bugs that I need to work on first, but this should be pretty 
straightforward to implement when I get to it.  

In the mean time, you could change the regular expression in the argument 
list to the processFiles() method in happydoclib/docset/docset_MultiFile.py.  
If you change it to also match for cgi files, you should be able to do what 
you need.  For example, r'^.*\.(py|cgi)$', works.  This would be a temporary 
solution, of course.

Doug

On Monday 21 January 2002 22:45, Lars Kellogg-Stedman wrote:
> Howdy,
>
> I'm interested in happydoc as a documentation tool, but I have thus far
> been unable to use it to create documentation for anything not ending in
> '.py'.  For instance, the following command:
>
>    happydoc script.cgi
>
> Generates no errors -- but it also generates no output.  There aren't
> any obvious command line options that seem relevant to this problem.
>
> Have I missed something simple?
>
> Thanks,
>
> -- Lars
>
>
> _______________________________________________
> HappyDoc-discuss mailing list
> Hap...@li...
> https://lists.sourceforge.net/lists/listinfo/happydoc-discuss