§
1j' ã óV — d dl mZmZ d dlmZmZmZmZ d dlm Z G d„ de¦ « Z
dS )é )ÚABCÚabstractmethod)ÚIterableÚListÚOptionalÚTuple)ÚMessagec óz — e Zd Zedeeeee f fd„¦ « Z ede
e fd„¦ « Z dS )ÚToolBaseÚreturnc ó — t ‚)a‡
Tools have their own way of being configured from configuration files
on the current path - for example, a .pep8rc file. Prospector will use
its own configuration settings unless this method discovers some
tool-specific configuration that should be used instead.
:return: A tuple: the first element is a string indicating how or where
this tool was configured from. For example, this can be a path
to the .pylintrc file used, if used. None means that prospector
defaults were used. The second element should be an iterable of
Message objects representing any issues which were found when
trying to load configuration - for example, bad values in a
.pylintrc file. It is also possible to simply return None if
neither value is useful.
©ÚNotImplementedError)ÚselfÚprospector_configÚ found_filess úg/builddir/build/BUILD/cloudlinux-venv-1.0.11/venv/lib/python3.11/site-packages/prospector/tools/base.pyÚ configurezToolBase.configure s
€ õ" "Ð!ó c ó — t ‚)zê
Actually run the tool and collect the various messages emitted by the tool.
It is expected that this will convert whatever output of the tool into the
standard prospector Message and Location objects.
r )r r s r Úrunz ToolBase.run s
€ õ "Ð!r N) Ú__name__Ú
__module__Ú __qualname__r r Ústrr r r r r r © r r r r sy € € € € € Øð"¸5ÀÀhÈxÐX_ÔO`ÔFaÐAaÔ;bð "ð "ð "ñ „^ð"ð$ ð" $ w¤-ð "ð "ð "ñ „^ð"ð "ð "r r N) Úabcr r Útypingr r r r Úprospector.messager r r r r úr s‡ ðØ #Ð #Ð #Ð #Ð #Ð #Ð #Ð #Ø 2Ð 2Ð 2Ð 2Ð 2Ð 2Ð 2Ð 2Ð 2Ð 2Ð 2Ð 2à &Ð &Ð &Ð &Ð &Ð &ð"ð "ð "ð "ð "ˆsñ "ô "ð "ð "ð "r