+ Pj^RIt^RIt^RIHt^RIHt^RIHtRtRt Rt Rt ]P3R R llt ]P3R R llt!R R]4tR#)N)RawConfigParser)py39)SetuptoolsDeprecationWarningc\V\4'd\P!RV4#VP R4p\P!RV4pVP R4pV# \ dT#i;i)NFDutf-8) isinstancestr unicodedata normalizedecodeencode UnicodeError)paths&q/Users/ahmed/devFolder/Ultron/claude-voice/gateway/.venv/lib/python3.14/site-packages/setuptools/unicode_utils.py decomposer su$$$UD11 {{7#$$UD1{{7# K   K s9A** A98A9c`\V\4'd\P!RV4#T#)a Return *text* in a canonical Unicode form (NFC) so that names which are visually identical but encoded differently compare equal. macOS APFS/HFS+ store file names in decomposed form (NFD), while patterns in ``MANIFEST.in`` are typically authored composed (NFC). The two denote the same file but differ byte-for-byte, so matching them directly lets an exclusion silently fail. Normalizing both the walked path and the pattern to a single form before matching avoids that (GHSA-h35f-9h28-mq5c). NFC)r r r r )texts&rr r s(2B B1 B- &B1-B1c4V^8dQhR\R\RR/#)r$cfgr%r&N)rr )r's"rr(r(Qs$ 3 3  3 # 3  3rcVPVRR7R# \d=\PYR7TP 4TPYR7R#i;i)zSame idea as :func:`_read_utf8_with_fallback`, but for the :meth:`RawConfigParser.read` method. This method may call ``cfg.clear()``. rr+r-N)r0rr1r2clear)r6r%r.s&&&r_cfg_read_utf8_with_fallbackr9QsN3 ( 3  d P  23sAAAc]tRt^atRtRtRtR#)r1zZ `encoding="utf-8"` fails with {file!r}, trying `encoding={fallback_encoding!r}`. a Fallback behavior for UTF-8 is considered **deprecated** and future versions of `setuptools` may not implement it. Please encode {file!r} with "utf-8" to ensure future builds will succeed. If this file was produced by `setuptools` itself, cleaning up the cached files and re-building/re-installing the package with a newer version of `setuptools` (e.g. by updating `build-system.requires` in its `pyproject.toml`) might solve the problem. N)__name__ __module__ __qualname____firstlineno___SUMMARY_DETAILS__static_attributes__r;rrr1r1asH Hrr1)rr configparserrcompatrwarningsrrr rr"LOCALE_ENCODINGr4r9r1r;rrrGsV (2  Q*;?:N:N "8<7K7K 3 6r