warning: Member try (variable) of namespace lib_validation is not documented.

[splint33]

Hello everyone, I am currently using Doxygen 1.9.7 (Dev build with the fix for the issue 9839).
I am using it to generate a documentation on multiple python custom packages.
On one of them, I think there is an issue.

There is an extract of the init.py file of my package:

# -*-coding:utf-8 -*

##	@file		__init__.py 
##	@date		XXXX/XX/XX
##	@author		XXX, XXX
##	@brief		XXX
##	
##	@details	XXX


##	@package	XXX
##	@brief		XXX


# Python library modules importation
#	-- None --
# Third party modules importation 
import urllib3
#	Project modules importation 
XXX


try:
	.......
except TestConfigError:
	.......

When generating the documentation, Doxygen raise a warning on the try statement.
It looks like it is interpreting it as a variable:

init.py:40: warning: Member try (variable) of namespace XXX is not documented.

I don't think there is a need in documenting a try statement in Python, but I could be wrong.

[albert-github]

Indeed there is no need to document the try:, doxygen sees it as a variable:

Please always mention the full doxygen version, especially when using the master / development version (i.e. the result of doxygen -v).

Problem is reproducible with a default Doxyfile in version 1.9.7 (2ac024c

[albert-github]

In the doxygen code I see that lines starting with an identified followed by a color (:) are to be considered as a variable like in e.g.

    nsmap = {
        prefix: uri
        for node in rootNode.iter()
        for (prefix, uri) in node.nsmap.items()
        if prefix is not None
    }

looks like that an exception has to be made for try: and else: and ...

[albert-github]

I've just pushed a proposed patch, pull request #9943

[splint33]

Just tested with your patch (1.9.7 (b4e95d3*)), it seems to resolve the issue !

[albert-github]

Code has been integrated in master on GitHub (please don't close the issue as this will be done at the moment of an official release).

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.9.7.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).