܎j/UddlmZddlZddlZddlmZmZddlmZddl Z ddl m Z ddl m Z dd lmZd gZejeZd ed <ejZeZd ed<ddZddZddZGdd e jZdS)) annotationsN) GeneratorAsyncGenerator)override) TokenCache)asyncify)OAUTH_API_BETA_HEADERAccessTokenAuthzlogging.Loggerlogzset[str]_warn_once_seenkeystrmessageargsobjectreturnNonect5|tvr ddddSt|dddn #1swxYwYtj|g|RdS)z8Emit a log warning at most once per ``key`` per process.N)_warn_once_lockraddr warning)rrrs MC:\Projects\DSCons\.venv\Lib\site-packages\anthropic\lib\credentials\_auth.py _warn_oncers !! / ! ! !!!!!!!! C   !!!!!!!!!!!!!!!K$s AAA  A paramc.td|d|dS)agWarn that an explicit ``api_key=`` / ``auth_token=`` argument shadows an explicit ``credentials=`` provider passed to the same constructor or ``copy()`` call. The static credential wins at the request-header level (``AccessTokenAuth.sync_auth_flow`` short-circuits on the pre-set header), which silently disables the credentials provider. zexplicit-shadow:z`%s=` was passed alongside `credentials=`; the static credential takes precedence and the credentials provider is silently disabled. Pass only one.Nr)rs r(warn_explicit_static_shadows_credentialsrs5"5""   env_varc0td|d||dS)aWarn that an ``ANTHROPIC_API_KEY`` / ``ANTHROPIC_AUTH_TOKEN`` from the environment is shadowing the SDK's profile / federation auto-discovery. Per the credential-precedence spec, a static-credential env var silently disables the auto-discovered federation and profile paths. Surface a one-shot warning so migrating users can see why their ``ANTHROPIC_PROFILE`` or WIF env vars are being ignored. z env-shadow:z%s is set and takes precedence over the SDK's profile / federation auto-discovery; unset %s to use the auto-discovered credential.Nr)r!s r&warn_env_static_shadows_auto_discoveryr#/s7g J r cneZdZdZdZddZedd ZddZe ddZ e ddZ dS)r uAdapts a :class:`TokenCache` to httpx's :class:`~httpx.Auth` protocol. Used by :meth:`anthropic.Anthropic.custom_auth` to inject ``Authorization: Bearer`` plus the OAuth beta header on every request, with proactive refresh handled by :class:`TokenCache`. Static credentials shadow federation: if the outgoing request already carries an ``X-Api-Key`` or ``Authorization`` header (set by the client's api_key / auth_token path), this auth flow is a no-op. That matches the Go SDK's ``authMiddleware`` and the documented precedence in the WIF user guide — a static ``ANTHROPIC_API_KEY`` shadows any credentials provider. F token_cacherrrc||_dSN) _token_cache)selfr%s r__init__zAccessTokenAuth.__init__Qs'r request httpx.Requestboolct|jdp|jdS)Nz X-Api-Key Authorization)r-headersget)r+s r_has_static_credentialz&AccessTokenAuth._has_static_credentialTs5GO'' 44\8K8KO8\8\]]]r tokenrcd||jd<|jdd}d|dD}t|vr9|td||jd<dSdS)NzBearer r/zanthropic-betac^g|]*}||+S)strip).0flags r z*AccessTokenAuth._apply..cs-\\\4tzz||\$**,,\\\r ,z, )r0r1splitr appendjoin)r)r+r3 existing_betaexisting_flagss r_applyzAccessTokenAuth._applyXs+r`sV""""""",,,,,,,,&&&&&& ------  'g'111111 ).""CEE!!!!         $:::::ej:::::r