o g( @sUdZddlmZddlZddlZddlZddlZddlmZddl m Z ddl m Z m Z mZejejejejeddZejvegejd dddlZd d lmZmZd d lmZd d lmZm Z d dl!m"Z"d dl#m$Z$d dl%m&Z&d dl'm(Z(ddl)Z*ddl+m,Z,gdZ-e dddZ.dZ/ej0Z1e j0Z2ddZ3ddZ4ddZ5e*j6j5je5_e rddl7m8Z8e*j6j9Z:de;d<nefd#d$Z?Gd%d&d&e@ZAeBdS)'z@Extensions to the 'distutils' for large or complex distributions) annotationsN)abstractmethod)Mapping) TYPE_CHECKINGTypeVaroverload setuptools_vendor backports)loggingmonkey)Require) PackageFinderPEP420PackageFinder) Distribution) Extension) __version__)SetuptoolsDeprecationWarning)DistutilsOptionError)setuprCommandrrr find_packagesfind_namespace_packages _CommandT_Command)boundcCs>Gdddtjj}||}|jdd|jrt|dSdS)Ncs8eZdZdZd fdd Zd fdd Zd d ZZS) z4_install_setup_requires..MinimalDistributionzl A minimal version of a distribution for supporting the fetch_build_eggs interface. attrsMapping[str, object]cs<d}fddt|t@D}t||jdS)N)dependency_linkssetup_requirescsi|]}||qSr!).0krr!P/var/www/rescue_company/venv/lib/python3.10/site-packages/setuptools/__init__.py AszQ_install_setup_requires..MinimalDistribution.__init__..)setsuper__init__ set_defaults_disable)selfr_inclfiltered __class__r$r%r)?s z=_install_setup_requires..MinimalDistribution.__init__Ncs6z t|\}}W|dfSty|dfYSw)zAIgnore ``pyproject.toml``, they are not related to setup_requiresr!)r( _split_standard_project_metadata Exception)r, filenamescfgtomlr/r!r%_get_project_config_filesFs  zN_install_setup_requires..MinimalDistribution._get_project_config_filescSsdS)zl Disable finalize_options to avoid building the working set. Ref #2158. Nr!r,r!r!r%finalize_optionsNszE_install_setup_requires..MinimalDistribution.finalize_options)rrN)__name__ __module__ __qualname____doc__r)r6r8 __classcell__r!r!r/r%MinimalDistribution9s r?T)ignore_option_errors) distutilscorerparse_config_filesr _fetch_build_eggs)rr?distr!r!r%_install_setup_requires6s   rFc Csfz ||jWdSty2}zd}d|jjvr-t|dr$|||d|dd}~ww)Na It is possible a package already installed in your system contains an version that is invalid according to PEP 440. You can try `pip install --use-pep517` as a workaround for this problem, or rely on a new virtual environment. If the problem refers to a package that is not installed yet, please contact that package's maintainers or distributors. InvalidVersionadd_note )fetch_build_eggsr r2r0r:hasattrrHannounce)rEexmsgr!r!r%rD\s  rDcKs"tt|tjjdi|S)Nr!)r configurerFrArBrr$r!r!r%rqsr) TypeAliasrPcseZdZUdZdZded<d fdd Zd!d d Zd d Ze d"d#ddZ e d"d$ddZ d"d%ddZ e d&ddZ e d&ddZ e d&ddZZS)'ra# Setuptools internal actions are organized using a *command design pattern*. This means that each action (or group of closely related actions) executed during the build should be implemented as a ``Command`` subclass. These commands are abstractions and do not necessarily correspond to a command that can (or should) be executed via a terminal, in a CLI fashion (although historically they would). When creating a new command from scratch, custom defined classes **SHOULD** inherit from ``setuptools.Command`` and implement a few mandatory methods. Between these mandatory methods, are listed: :meth:`initialize_options`, :meth:`finalize_options` and :meth:`run`. A useful analogy for command classes is to think of them as subroutines with local variables called "options". The options are "declared" in :meth:`initialize_options` and "defined" (given their final values, aka "finalized") in :meth:`finalize_options`, both of which must be defined by every command class. The "body" of the subroutine, (where it does all the work) is the :meth:`run` method. Between :meth:`initialize_options` and :meth:`finalize_options`, ``setuptools`` may set the values for options/attributes based on user's input (or circumstance), which means that the implementation should be careful to not overwrite values in :meth:`finalize_options` unless necessary. Please note that other commands (or other parts of setuptools) may also overwrite the values of the command's options/attributes multiple times during the build process. Therefore it is important to consistently implement :meth:`initialize_options` and :meth:`finalize_options`. For example, all derived attributes (or attributes that depend on the value of other attributes) **SHOULD** be recomputed in :meth:`finalize_options`. When overwriting existing commands, custom defined classes **MUST** abide by the same APIs implemented by the original class. They also **SHOULD** inherit from the original class. Fr distributionrEc st|t||dS)zj Construct the command for dist, updating vars(self) with any keyword parameters. N)r(r)varsupdate)r,rEkwr/r!r%r)s zCommand.__init__NcCsBt||}|durt||||St|tstd|||f|S)Nz'%s' must be a %s (got `%s`))getattrsetattr isinstancestrr)r,optionwhatdefaultvalr!r!r%_ensure_stringlikes    zCommand._ensure_stringlikecCsrt||}|dur dSt|trt||td|dSt|tr+tdd|D}nd}|s7td||fdS)aEnsure that 'option' is a list of strings. If 'option' is currently a string, we split it either on /,\s*/ or /\s+/, so "foo bar baz", "foo,bar,baz", and "foo, bar baz" all become ["foo", "bar", "baz"]. .. TODO: This method seems to be similar to the one in ``distutils.cmd`` Probably it is just here for backward compatibility with old Python versions? :meta private: Nz,\s*|\s+css|]}t|tVqdSr9)rWrX)r"vr!r!r% sz-Command.ensure_string_list..Fz''%s' must be a list of strings (got %r)) rUrWrXrVresplitlistallr)r,rYr\okr!r!r%ensure_string_lists    zCommand.ensure_string_listcommandrXreinit_subcommandsboolreturnrcKdSr9r!r,rfrgrTr!r!r%reinitialize_commandzCommand.reinitialize_commandrcKrjr9r!rkr!r!r%rlrmstr | _CommandcKs t|||}t|||Sr9)rrlrRrS)r,rfrgrTcmdr!r!r%rlsNonecCt)z Set or (reset) all options/attributes/caches used by the command to their default values. Note that these values may be overwritten during the build. NotImplementedErrorr7r!r!r%initialize_optionszCommand.initialize_optionscCrq)z Set final values for all options/attributes used by the command. Most of the time, each option/attribute/cache should only be set if it does not have any value yet (e.g. ``if self.attr is None: self.attr = val``). rrr7r!r!r%r8ruzCommand.finalize_optionscCrq)z Execute the actions intended by the command. (Side effects **SHOULD** only take place when :meth:`run` is executed, for example, creating new files or writing to the terminal output). rrr7r!r!r%runruz Command.run)rErr9)F)rfrXrgrhrir)rfrrgrhrir)rfrnrgrhrir)rirp)r:r;r<r=command_consumes_arguments__annotations__r)r]rerrlrrtr8rvr>r!r!r/r%rs* %     rcCs&ddtj|ddD}ttjj|S)z% Find all files under 'path' css.|]\}}}|D] }tj||Vq qdSr9)ospathjoin)r"basedirsfilesfiler!r!r%r_ s z#_find_all_simple..T) followlinks)rywalkfilterrzisfile)rzresultsr!r!r%_find_all_simples rcCs6t|}|tjkrtjtjj|d}t||}t|S)z Find all files under 'dir' and return the list of full filenames. Unless dir is '.', return full filenames with dir prepended. )start) rrycurdir functoolspartialrzrelpathmaprb)dirr~make_relr!r!r%findalls   rc@seZdZdZdS)sicz;Treat this string as-is (https://en.wikipedia.org/wiki/Sic)N)r:r;r<r=r!r!r!r%rsr)Cr= __future__rrryr`sysabcrcollections.abcrtypingrrrrzextendr{dirname__file__ vendor_pathmodulespop_distutils_hack.override_distutils_hackr r dependsr discoveryrrrEr extensionrversionrwarningsrdistutils.corerAdistutils.errorsr__all__rbootstrap_install_fromfindrrrFrDrrBtyping_extensionsrPrrrx get_unpatchedrrrrXr patch_allr!r!r!r%sP   8       &