eUdZddlZddlZddlmZmZmZmZmZddl m Z ddl m Z dZGddeZdaeed < d(d eeefd eed ed edeedeeddfdZd)dZddddedeedeedeedeeddf dZGddZeddddd !Zed"d#dd$d %Zed&d#dd'd %ZdS)*zN A module that implements tooling to enable easy warnings about deprecations. N)AnyOptionalTextIOTypeUnion)parse) __version__z DEPRECATION: ceZdZdS)PipDeprecationWarningN)__name__ __module__ __qualname__V/var/www/html/api/venv/lib/python3.11/site-packages/pip/_internal/utils/deprecation.pyr r sDrr _original_showwarningmessagecategoryfilenamelinenofilelinereturnc|tt||||||dSdSt|tr+tjd}||dSt||||||dS)Nzpip._internal.deprecations)r issubclassr logging getLoggerwarning)rrrrrrloggers r _showwarningr s  , !'8XvtT R R R R R - , H3 4 4O"#?@@wgx64NNNNNrctjdtdttjat t_dSdS)NdefaultT)append)warnings simplefilterr r showwarningr rrrinstall_warning_loggerr',sB )%:4HHHH$ ( 4+%$r) feature_flagissuereason replacementgone_inr(r)c2|duo$ttt|k}|tdf||sdndf|df||sdndf|dfg}dd |D}|rt |t j|td 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/{} c3NK|] \}}|| ||V!dSN)format).0value format_strs r zdeprecated..nsK E:  !e&7 %  &7&7&7&7r)r stacklevel)rcurrent_versionDEPRECATION_MSG_PREFIXjoinr r$warn)r*r+r,r(r)is_gone message_partsrs r deprecatedr>7s:T!NeO&<&<g&NG *0001  > 8 8=    +   S S    N %M0hh!.G-#G,,, M'$9aHHHHHHrceZdZ ddedeedeedeedeeded efd Zd ed dfd ZdS)LegacyInstallReasonNFr*r+r,r(r)emit_after_successemit_before_installch||_||_||_||_||_||_||_dSr0)_reason _replacement_gone_in _feature_flag_issuerArB)selfr*r+r,r(r)rArBs r__init__zLegacyInstallReason.__init__|s? ' ) "4#6   rnamerct|j||j|j|j|jdS)N)rK)r*r+r,r(r))r>rDr1rErFrGrH)rIrKs remit_deprecationz$LegacyInstallReason.emit_deprecationsO<&&D&11)M++       r)NNNNFF) r r rstrrintboolrJrMrrrr@r@{s&*!%&*##($)777c]7# 7 sm 7 } 7!7"7777$ S T      rr@zk{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)rAz{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)rBz{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)rN)__doc__rr$typingrrrrrpip._vendor.packaging.versionrpipr r8r9Warningr r__annotations__rNrOr r'r>r@#LegacyInstallReasonFailedBdistWheel&LegacyInstallReasonMissingWheelPackage2LegacyInstallReasonNoBinaryForcesSetuptoolsInstallrrrrZs55555555555555//////......(     G   "s!!!" OO 7C< O7mOO  O 6  O 3- O OOOO(,,,, #' AIAIAI AI#AIc] AI 3- AI C= AI AIAIAIAIH        :':&9 =>   ' ' '#*=)<  6   * * *&6I5H . 6   6 6 6222r