§ Z}¨Áç&Aƒãó€—ddlZddlZddlmZddlmZddlmZm Z dZ ejd¦«jZ d„Zd„Zdd „ZdS)éN)ÚOutputChoice)Ú FORMATTERS)Ú DEFAULT_TOOLSÚTOOLS)Ú build_managerÚ prospectorcóv—tjd¦«}| tjdd¬¦«¦«| tjdd¬¦«¦«| tjdtjg¬¦«¦«| tjdd¬¦«¦«| tjd d¬¦«¦«| tjd d¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjd d¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjdtttj ¦«¦«¦«d¬¦«¦«| tjdd¬¦«¦«| tjdtjttj ¦«¦«¦«d¬¦«¦«| tjdtjg¬¦«¦«| tjdtjg¬¦«¦«| tjdtjg¬¦«¦«| tjdtjg¬¦«¦«| tj dgd¢d¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjdd¬¦«¦«| tjd tjg¬¦«¦«| tjd!tjg¬¦«¦«| tjd"d¬¦«¦«| tjd#d¬¦«¦«| tjd$d¬¦«¦«|S)%NrÚ zero_exitF)ÚdefaultÚ autodetectTÚusesÚblendingÚdoc_warningsÚ test_warningsÚno_style_warningsÚmember_warningsÚ full_pep8Úmax_line_lengthÚ messages_onlyÚsummary_onlyÚquietÚ output_formatÚabsolute_pathsÚtoolsÚ with_toolsÚ without_toolsÚprofilesÚprofile_pathÚ strictness)ÚveryhighÚhighÚmediumÚlowÚverylowÚshow_profileÚno_external_configÚlegacy_tool_namesÚpylint_config_fileÚpathÚignore_patternsÚignore_pathsÚdie_on_tool_errorÚinclude_tool_stdoutÚdirect_tool_stdout)ÚsocÚConfigurationManagerÚaddÚBooleanSettingÚListSettingÚStringÚIntegerSettingrÚsortedrÚkeysÚChoicerÚ ChoiceSettingÚ StringSetting)Úmanagers úq/builddir/build/BUILD/cloudlinux-venv-1.0.10/venv/lib/python3.11/site-packages/prospector/config/configuration.pyrrsÅ€ÝÔ& |Ñ4Ô4€Gà‡K‚K•Ô" ;¸Ð>Ñ>Ô>Ñ?Ô?Ð?à‡K‚K•Ô" <¸Ð>Ñ>Ô>Ñ?Ô?Ð?Ø‡K‚K•” ¬ ¸BÐ?Ñ?Ô?Ñ@Ô@Ð@à‡K‚K•Ô" :°tÐ<Ñ<Ô<Ñ=Ô=Ð=à‡K‚K•Ô" >¸4Ð@Ñ@Ô@ÑAÔAÐAØ‡K‚K•Ô" ?¸DÐAÑAÔAÑBÔBÐBØ‡K‚K•Ô"Ð#6ÀÐEÑEÔEÑFÔFÐFØ‡K‚K•Ô"Ð#4¸dÐCÑCÔCÑDÔDÐDØ‡K‚K•Ô" ;¸Ð=Ñ=Ô=Ñ>Ô>Ð>Ø‡K‚K•Ô"Ð#4¸dÐCÑCÔCÑDÔDÐDà‡K‚K•Ô" ?¸EÐBÑBÔBÑCÔCÐCØ‡K‚K•Ô" >¸5ÐAÑAÔAÑBÔBÐBØ‡K‚K•Ô" 7°EÐ:Ñ:Ô:Ñ;Ô;Ð;Ø‡K‚KÝŒØÝ¥ ¤Ñ 1Ô 1Ñ2Ô2Ñ3Ô3Øð ñ ô ñôðð‡K‚K•Ô"Ð#3¸UÐCÑCÔCÑDÔDÐDà‡K‚KÝŒØÝŒJ•veœj™lœlÑ+Ô+Ñ,Ô,Øð ñ ô ñôðð‡K‚K•” c¬jÀ"ÐEÑEÔEÑFÔFÐFØ‡K‚K•” µ´ÀRÐHÑHÔHÑIÔIÐIØ‡K‚K•” C¬JÀÐCÑCÔCÑDÔDÐDØ‡K‚K•” µ´ ÀBÐGÑGÔGÑHÔHÐHØ‡K‚KÝÔØØ<Ð<Ð<Øð ñ ô ñôðð‡K‚K•Ô" >¸5ÐAÑAÔAÑBÔBÐBà‡K‚K•Ô"Ð#7ÀÐGÑGÔGÑHÔHÐHØ‡K‚K•Ô"Ð#6ÀÐFÑFÔFÑGÔGÐGØ‡K‚K•Ô!Ð"6ÀÐEÑEÔEÑFÔFÐFà‡K‚K•Ô! &°$Ð7Ñ7Ô7Ñ8Ô8Ð8à‡K‚K•”Ð 1µ3´:ÀrÐJÑJÔJÑKÔKÐKØ‡K‚K•” µ´ ÀBÐGÑGÔGÑHÔHÐHà‡K‚K•Ô"Ð#6ÀÐFÑFÔFÑGÔGÐGØ‡K‚K•Ô"Ð#8À%ÐHÑHÔHÑIÔIÐIØ‡K‚K•Ô"Ð#7ÀÐGÑGÔGÑHÔHÐHà€Nóc óà—t¦«tj¦«tjd¦«tjtjd¦«tjd¦«f¦«g}|S)N)ú .prospectorrcz setup.cfgztox.inir?)Úbuild_command_line_sourcer/ÚEnvironmentVariableSourceÚConfigFileSourceÚConfigDirectoryÚ HomeDirectory)Úsourcess r<Úbuild_default_sourcesrFOsm€å!Ñ#Ô#ÝÔ%Ñ'Ô'ÝÔð ñ ô õ ÔåÔ# OÑ4Ô4ÝÔ! /Ñ2Ô2ð ñ ô ð€Gð$€Nr=ú'Performs static analysis of Python codecó—i}|||d<|||d<idddgddœ“dd d gddœ“dd dgddœ“dddgddœ“dddgddœ“dddgddœ“ddgddœ“dd d!gd"dœ“d#d$d%gd&dœ“d'd(d)gd*dœ“d+d,d-gd.dœ“d/d0gd1dœ“d2d3d4gd5dœ“d6d7d8gd9dœ“d:d;d ttj¦«¦«¦«›d?dœ“d@dAdBi“dCdDdEgdFd> tt j¦«¦«¦«›dGd> tt ¦«¦«›dœ“dHdIgdJd> tt j¦«¦«¦«zdœdKdLgdMd> tt j¦«¦«¦«zdœdNdOgdPdœdQgdRdœdSgdTdœdUdVgdWdœdXdYgdZdœd[gd\dœd]d^gd_dœd`dagdbdœdcddgdedœdfgdgdœdhgdidœdjdkgdldœdmœ¥}dndodpdqdrœff}t j|t||¬s¦«S)tNÚprogÚdescriptionr z-0z--zero-exitaIProspector will exit with a code of 1 (one) if any messages are found. This makes automation easier; if there are any problems at all, the exit code is non-zero. However this behaviour is not always desirable, so if this flag is set, prospector will exit with a code of 0 if it ran successfully, and non-zero if it failed to run.)ÚflagsÚhelprz-Az--no-autodetectzTurn off auto-detection of frameworks and libraries used. By default, autodetection will be used. To specify manually, see the --uses option.r z-uz--useszàA list of one or more libraries or frameworks that the project uses. Possible values are: django, celery, flask. This will be autodetected by default, but if autodetection doesn't work, manually specify them using this flag.rz-Bz --no-blendingz«Turn off blending of messages. Prospector will merge together messages from different tools if they represent the same error. Use this option to see all unmerged messages.rz-Dz--doc-warningsz%Include warnings about documentation.rz-Tz--test-warningsz%Also check test modules and packages.r'z--legacy-tool-nameszcOutput deprecated names for tools (pep8, pep257) instead of updated names (pycodestyle, pydocstyle)rz-8z--no-style-warningszeDon't create any warnings about style. This disables the PEP8 tool and similar checks for formatting.rz-mz--member-warningszAttempt to warn when code tries to access an attribute of a class or member of a module which does not exist. This is disabled by default as it tends to be quite inaccurate.rz-qz--quietzqRun but do not output anything to stdout. Useful to suppress output in scripts without sending to a file (via -o)rz-Fz--full-pep8zNEnables every PEP8 warning, so that all PEP8 style violation will be reported.rz--max-line-lengthzgThe maximum line length allowed. This will be set by the strictness if no value is explicitly specifiedrz-Mz--messages-onlyzSOnly output message information (don't output summary information about the checks)rz-Sz--summary-onlyzROnly output summary information about the checks (don'toutput message information)rz-oz--output-formatz%The output format. Valid values are: z, zŠ. This will output to stdout by default, however a target file can be used instead by adding :path-to-output-file, eg, -o json:output.jsonrrLz{Whether to output absolute paths when referencing files in messages. By default, paths will be relative to the project pathrz-tz--toolzA list of tools to run. This lets you set exactly which tools to run. To add extra tools to the defaults, see --with-tool. Possible values are: z/. By default, the following tools will be run: z-wz--with-toolzŠA list of tools to run in addition to the default tools. To specify all tools explicitly, use the --tool argument. Possible values are %s.z-Wz--without-toolz²A list of tools that should not be run. Useful to turn off only a single tool from the defaults. To specify all tools explicitly, use the --tool argument. Possible values are %s.z-Pz --profilea The list of profiles to load. A profile is a certain 'type' of behaviour for prospector, and is represented by a YAML configuration file. Either a full path to the YAML file describing the profile must be provided, or it must be on the profile path (see --profile-path)z--profile-pathz³Additional paths to search for profile files. By default this is the path that prospector will check, and a directory called ".prospector" in the path that prospector will check.z--show-profilea-Include the computed profile in the summary. This will show what prospector has decided the overall profile is once all profiles have been combined and inherited from. This will produce a large output in most cases so is only useful when trying to debug why prospector is not behaving like you expect.z-sz--strictnesszÌHow strict the checker should be. This affects how harshly the checker will enforce coding guidelines. The default value is "medium", possible values are "veryhigh", "high", "medium", "low" and "verylow".z-Ez--no-external-configa]Determines how prospector should behave when configuration already exists for a tool. By default, prospector will use existing configuration. This flag will cause prospector to ignore existing configuration and use its own settings for every tool. Note that prospector will always use its own config for tools which do not have custom configuration.z--pylint-config-filezµThe path to a pylintrc file to use to configure pylint. Prospector will find .pylintrc files in the root of the project, but you can use this option to specify manually where it is.z-Iz--ignore-patternsz‘A list of paths to ignore, as a list of regular expressions. Files and folders will be ignored if their full path contains any of these patterns.z-iz--ignore-pathsz¨A list of file or directory names to ignore. If the complete name matches any of the items in this list, the file or directory (and all subdirectories) will be ignored.z-Xz--die-on-tool-errorzºIf a tool fails to run, prospector will try to carry on. Use this flag to cause prospector to die and raise the exception the tool generated. Mostly useful for development on prospector.z--include-tool-stdouta^There are various places where tools will output warnings to stdout/stderr, which breaks parsing of JSON output. Therefore while tols is running, this is suppressed. For developing, it is sometimes useful to see this. This flag will cause stdout/stderr from a tool to be shown as a normal message amongst other warnings. See also --direct-tool-stdoutz--direct-tool-stdoutziSame as --include-tool-stdout, except the output will be printed directly rather than shown as a message.z-pz--pathzÒThe path to a Python project to inspect. Defaults to PWD if not specified. Note: This command line argument is deprecated and will be removed in a future update. Please use the positional PATH argument instead.)rrrrr%rr&r(r*r+r,zinclude-tool-stdoutzdirect-tool-stdoutr)Ú checkpathz–The path to a Python project to inspect. Defaults to PWD if not specified. If multiple paths are specified, they must all be files (no directories).ÚPATHÚ*)rLÚmetavarÚnargs)ÚoptionsÚversionÚparser_optionsÚ positional) Újoinr6rr7rrr/ÚCommandLineSourceÚ_VERSION)rIrJrTrRrUs r<r@r@esî€Ø€NØÐØ!%ˆvÑØÐØ(3ˆ}Ñ%ðDØØ˜MÐ*ð!ð ð ðDð ØÐ-Ð.ð0ð ð ðDð Ø˜HÐ%ð<ð ð ð!Dð. Ø˜OÐ,ðð ð ð/Dð< ØÐ,Ð-Ø;ð ð ð=DðD ØÐ-Ð.Ø;ð ð ðEDðL Ø+Ð,ðAð ð ðMDðV ØÐ1Ð2ð<ð ð ðWDð` ØÐ/Ð0ð=ð ð ðaDðl Ø˜IÐ&ðCð ð ðmDðv Ø˜MÐ*Ødð ð ðwDð~ Ø)Ð*ð-ð ð ðDðH ØÐ-Ð.Ølð ð ðIDðP ØÐ,Ð-Økð ð ðQDðX ØÐ-Ð.Ð.ðyŠy¥ ¤Ñ 1Ô 1Ñ2Ô2Ñ3Ô3Ð3Ð3ð6ð ð ðYDðd Øðð ðeDðn Ø˜HÐ%Ð%ð— ’ &¥¤¡¤Ñ.Ô.Ñ/Ô/Ð/Ð/Ø— ’ &¥Ñ/Ô/Ñ0Ô0Ð0ð ð ð ðoDðF˜MÐ*ð&à)-¯ªµ6½%¼*¹,¼,Ñ3GÔ3GÑ)HÔ)HñJð ð ðÐ,Ð-ð&ð*.¯ªµ6½%¼*¹,¼,Ñ3GÔ3GÑ)HÔ)HñJð ð ð˜KÐ(ð8ð ð ð'Ð'ðLð ð ð'Ð'ð;ð ð ð˜NÐ+ðBð ð ðÐ2Ð3ð1ð ð ð-Ð-ð,ð ð ðÐ/Ð0ð9ð ð ðÐ,Ð-ðð ð ðÐ1Ð2ð*ð ð ð.Ð.ðUð ð ð-Ð-ð7ð ð ð˜HÐ%ð9ð ð ð{DðDðD€GðP ð=ð"Øð ð ð ð€JõÔ ØÝØ%Øð ñôðr=)NrG)Ú pkg_resourcesÚ setoptconfr/Úprospector.config.datatyperÚprospector.formattersrÚprospector.toolsrrÚ__all__Úget_distributionrSrXrrFr@©r=r<úras¶ðàÐÐÐØÐÐÐà3Ð3Ð3Ð3Ð3Ð3Ø,Ð,Ð,Ð,Ð,Ð,Ø1Ð1Ð1Ð1Ð1Ð1Ð1Ð1à €à)ˆ=Ô)¨,Ñ7Ô7Ô?€ð>ð>ð>ðBððð,_ð_ð_ð_ð_ð_r=