a Sic @s UdZddlZddlZddlmZmZmZmZmZddl m Z ddl m Z dZGdddeZdaeed <d"eeefeeeeeeeedd d d Zdd ddZdddeeeeeeeeeddddZGdddZeddddddZeddddddZed ddd!ddZdS)#zN A module that implements tooling to enable easy warnings about deprecations. N)AnyOptionalTextIOTypeUnion)parse) __version__z DEPRECATION: c@s eZdZdS)PipDeprecationWarningN)__name__ __module__ __qualname__r r [/var/www/html/django/DPS/env/lib/python3.9/site-packages/pip/_internal/utils/deprecation.pyr sr _original_showwarning)messagecategoryfilenamelinenofilelinereturncCsZ|dur$tdurVt||||||n2t|trDtd}||nt||||||dS)Nzpip._internal.deprecations)r issubclassr logging getLoggerwarning)rrrrrrloggerr r r _showwarnings   r)rcCs(tjdtddtdur$tjatt_dS)NdefaultT)append)warnings simplefilterr r showwarningrr r r rinstall_warning_logger,sr") feature_flagissue)reason replacementgone_inr#r$rcCs|duottt|k}|tdf||s.dndf|df||sBdndf|dfg}dd d |D}|rpt|tj|td d dS) aHelper to deprecate existing functionality. reason: Textual reason shown to the user about why this functionality has been deprecated. Should be a complete sentence. replacement: Textual suggestion shown to the user about what alternative functionality they can use. gone_in: The version of pip does this functionality should get removed in. Raises an error if pip's current version is greater than or equal to this. feature_flag: Command-line flag of the form --use-feature={feature_flag} for testing upcoming functionality. issue: Issue number on the tracker that would serve as a useful place for users to find related discussion and provide feedback. Nz{}z*pip {} will enforce this behaviour change.z*Since pip {}, this is no longer supported.zA possible replacement is {}.zEYou can use the flag --use-feature={} to test the upcoming behaviour.z@Discussion can be found at https://github.com/pypa/pip/issues/{} css,|]$\}}|dur|dur||VqdSN)format).0valueZ format_strr r r nszdeprecated..)r stacklevel)rcurrent_versionDEPRECATION_MSG_PREFIXjoinr rwarn)r%r&r'r#r$Zis_goneZ message_partsrr r r deprecated7s2  r4c @sHeZdZd eeeeeeeeeeedddZeddddZdS) LegacyInstallReasonNF)r%r&r'r#r$emit_after_successemit_before_installcCs.||_||_||_||_||_||_||_dSr))_reason _replacement_gone_in _feature_flag_issuer6r7)selfr%r&r'r#r$r6r7r r r__init__|s zLegacyInstallReason.__init__)namercCs(t|jj|d|j|j|j|jddS)N)r?)r%r&r'r#r$)r4r8r*r9r:r;r<)r=r?r r remit_deprecations z$LegacyInstallReason.emit_deprecation)NNNNFF) r r r strrintboolr>r@r r r rr5{s  r5zk{name} was installed using the legacy 'setup.py install' method, because a wheel could not be built for it.z+to fix the wheel build issue reported abovez23.1i T)r%r&r'r$r6z{name} is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed.z#to enable the '--use-pep517' optionio!)r%r&r'r$r7z{name} is being installed using the legacy 'setup.py install' method, because the '--no-binary' option was enabled for it and this currently disables local wheel building for projects that don't have a 'pyproject.toml' file.i,)NN)__doc__rrtypingrrrrrpip._vendor.packaging.versionrpiprr0r1Warningr r__annotations__rArBrr"r4r5Z#LegacyInstallReasonFailedBdistWheelZ&LegacyInstallReasonMissingWheelPackageZ2LegacyInstallReasonNoBinaryForcesSetuptoolsInstallr r r rsh      D