Do not throw in parse_tag_file if the mappings is a single Entry instead of a FunctionList

[sea-bass]

I ran into a build error with the https://github.com/moveit/moveit2_tutorials repo and found that the parse_tag_file() had a mappings dictionary that expected entities to map to FunctionList objects, but many of them were Entry objects that could straightforwardly be packaged up into a FunctionList instead of throwing an exception.

I have no idea if this is correct, but it fixed the issue for me!

[JasperCraeghs]

I reproduced the error thrown during sphinx-build:

Extension error (sphinxcontrib.doxylink.doxylink):
Handler <function setup_doxylink_roles at 0x7c0d9a0f3eb0> for event 'builder-inited' threw an exception (exception: Cannot add override to non-function 'create_deprecated_headers::DeprecatedHeader::contents')

I think the cause is that contents is the name of both an attribute and a method. The code is functional, but it is bad practice. I suggest turning the attribute and method into a property.

I am hesitant to merge your workaround because of the added complexity that doesn't make sense. It discards the attribute in favor of the method, without reporting the duplicate name. @milliams do you have a suggestion on how to handle this corner case?

EDIT: I just realized that Doxylink doesn't officially support Python code. I'll create a new PR with a similar workaround, but more maintainable.

[JasperCraeghs]

PR #63 resolves this issue. I tested your use case (create_deprecated_headers::DeprecatedHeader::contents) and the Doxygen documentation for the method contents() is used as target, so not the attribute. Closing this.

[sea-bass]

PR #63 resolves this issue. I tested your use case (create_deprecated_headers::DeprecatedHeader::contents) and the Doxygen documentation for the method contents() is used as target, so not the attribute. Closing this.

Thank you -- confirming that it solved the issue: moveit/moveit2_tutorials#1012