doxypy

doxypy is an input filter for Doxygen. It preprocesses python files so that docstrings of classes and functions are extracted as Doxygens special python documentation blocks.

See the projects website for details: http://code.foosel.org/doxypy

Please keep in mind that you help us fixing your problem faster by providing a proper bug report. A simple "it doesn't work" won't help us in locating the problem; always state exactly **what** lead to **which** feature not working, and provide **examples** if possible. Please also refer to http://www.catb.org/~esr/faqs/smart-questions.html
Tasklist

FS#33 - errors when INLINE_SOURCES is set to YES

Attached to Project: doxypy
Opened by Anonymous Submitter - Tuesday, 11 November 2008, 22:27 GMT+2
Last edited by Gina Häußge (foosel) - Thursday, 13 November 2008, 11:21 GMT+2
Task Type Bug Report
Category Backend / Core
Status Closed
Assigned To Gina Häußge (foosel)
Operating System All
Severity Critical
Priority Normal
Reported Version 0.3rc1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I turn on the doxygen switch to inline sources into the documentation, errors are generated by doxypy. I see this in the stdout:

Traceback (most recent call last):
File "c:\projects\shared\tools/doxypy-0.3/doxypy.py", line 369, in ?
main()
File "c:\projects\shared\tools/doxypy-0.3/doxypy.py", line 366, in main
print output
IOError: (0, 'Error')
Traceback (most recent call last):
File "c:\projects\shared\tools/doxypy-0.3/doxypy.py", line 369, in ?
main()
File "c:\projects\shared\tools/doxypy-0.3/doxypy.py", line 366, in main
print output
IOError: (0, 'Error')
close failed: [Errno 22] Invalid argument
close failed: [Errno 22] Invalid argument
This task depends upon

Closed by  Gina Häußge (foosel)
Thursday, 13 November 2008, 11:21 GMT+2
Reason for closing:  Fixed
Additional comments about closing:  Looks like Doxygen closes the standard output prematurely when generating INLINE_SOURCES and all of INPUT_FILTER, FILTER_SOURCE_FILES and INLINE_SOURCES are set. I circumvented the error by catching the IOError at the line of code in question. It's a bit dirty, but it works. A new version (0.4) will be released within the day, just have to do a sanity check on the other stuff I did first.
Comment by Gina Häußge (foosel) - Tuesday, 11 November 2008, 22:41 GMT+2
Could you please provide a (minimal) example input for triggering this behaviour? I can't reproduce it myself.

Loading...