U ui}( @sdZddlmZddlZddlZddlZddlZddlmZddl m Z ddl m Z m Z mZejejejejeddZejkegejd 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,ddddddddgZ-e dddZ.dZ/ej0Z1e j0Z2ddZ3dd d!d"Z4d#dZ5e*j6j5je5_e rdd$l)m7Z8ne9e*j6j7Z8Gd%dde8Z7d&d'Z:ej;fd(d)Ze?dS),z@Extensions to the 'distutils' for large or complex distributions) annotationsN)abstractmethod)Mapping) TYPE_CHECKINGTypeVaroverload setuptools_vendorZ backports)loggingmonkey)Require) PackageFinderPEP420PackageFinder) Distribution) Extension) __version__)SetuptoolsDeprecationWarning)DistutilsOptionErrorsetuprCommandrr r find_packagesfind_namespace_packages _CommandT_Command)boundcCs:Gdddtjj}||}|jdd|jr6t|dS)Ncs<eZdZdZddfdd Zd fdd Zd d ZZS) z4_install_setup_requires..MinimalDistributionzl A minimal version of a distribution for supporting the fetch_build_eggs interface. zMapping[str, object]attrscs<d}fddt|t@D}t||jdS)N)Zdependency_linkssetup_requirescsi|]}||qSr).0krr7/tmp/pip-unpacked-wheel-9osl9suo/setuptools/__init__.py AszQ_install_setup_requires..MinimalDistribution.__init__..)setsuper__init__ set_defaults_disable)selfrZ_inclfiltered __class__rr"r&?s z=_install_setup_requires..MinimalDistribution.__init__Ncs:zt|\}}Wntk r0|dfYSX|dfS)zAIgnore ``pyproject.toml``, they are not related to setup_requiresr)r%Z _split_standard_project_metadata Exception)r) filenamescfgtomlr+rr"_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. Nrr)rrr"finalize_optionsNszE_install_setup_requires..MinimalDistribution.finalize_options)N)__name__ __module__ __qualname____doc__r&r1r3 __classcell__rrr+r"MinimalDistribution9sr9T)Zignore_option_errors) distutilscorerparse_config_filesr_fetch_build_eggs)rr9distrrr"_install_setup_requires6s  r?r>c Csrz||jWn\tk rl}z>d}d|jjkrZt|drH||n|d|dW5d}~XYnXdS)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 )Zfetch_build_eggsrr-r,r4hasattrrBannounce)r>exmsgrrr"r=\s   r=cKstt|tjjf|SN)r configurer?r:r;rrrrr"rqs)rcseZdZUdZdZded<ddfdd Zd d d Zd d d dZe d!d dddddZ e d"ddddddZ d#ddddddZ e ddddZ e ddddZ e ddddZZS)$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 distributionr@c st|t||dS)zj Construct the command for dist, updating vars(self) with any keyword parameters. N)r%r&varsupdate)r)r>kwr+rr"r&s zCommand.__init__NcCsBt||}|dkr"t||||St|ts>td|||f|S)Nz'%s' must be a %s (got `%s`))getattrsetattr isinstancestrr)r)optionwhatdefaultvalrrr"_ensure_stringlikes    zCommand._ensure_stringlikerQ)rRcCspt||}|dkrdSt|tr6t||td|n6t|trTtdd|D}nd}|sltd||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|tVqdSrH)rPrQ)r vrrr" sz-Command.ensure_string_list..Fz''%s' must be a list of strings (got %r)) rNrPrQrOresplitlistallr)r)rRrUokrrr"ensure_string_lists    zCommand.ensure_string_listboolr)commandreinit_subcommandsreturncKsdSrHrr)r`rarMrrr"reinitialize_commandszCommand.reinitialize_commandrcKsdSrHrrcrrr"rdszstr | _CommandcKs t|||}t|||SrH)rrdrKrL)r)r`rarMcmdrrr"rdsNone)rbcCstdS)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. NNotImplementedErrorr2rrr"initialize_optionsszCommand.initialize_optionscCstdS)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``). Nrgr2rrr"r3szCommand.finalize_optionscCstdS)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). Nrgr2rrr"runsz Command.run)N)F)F)F)r4r5r6r7Zcommand_consumes_arguments__annotations__r&rVr^rrdrrir3rjr8rrr+r"rs( % cCs&ddtj|ddD}ttjj|S)z% Find all files under 'path' css,|]$\}}}|D]}tj||VqqdSrH)ospathjoin)r basedirsfilesfilerrr"rXsz#_find_all_simple..T) followlinks)rlwalkfilterrmisfile)rmresultsrrr"_find_all_simples rxcCs6t|}|tjkr.tjtjj|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) rxrlcurdir functoolspartialrmrelpathmapr[)dirrqZmake_relrrr"findalls   rc@seZdZdZdS)sicz;Treat this string as-is (https://en.wikipedia.org/wiki/Sic)N)r4r5r6r7rrrr"rsr)@r7 __future__rr{rlrYsysabcrcollections.abcrtypingrrrrmextendrndirname__file__Z vendor_pathmodulespopZ_distutils_hack.overrideZ_distutils_hackr r dependsr Z discoveryrrr>r extensionrversionrwarningsrdistutils.corer:distutils.errorsr__all__rZbootstrap_install_fromfindrrr?r=rr;rrZ get_unpatchedrxrzrrQrZ patch_allrrrr"s\   8       &