հjddlZddlZddlmZddlmZddlmZdZdZ dZ d Z ejfd e d e fd Zejfd ed e d dfdZGddeZy)N)RawConfigParser)py39)SetuptoolsDeprecationWarningct|trtjd|S |j d}tjd|}|j d}|S#t $rY|SwxYw)NNFDutf-8) isinstancestr unicodedata normalizedecodeencode UnicodeError)paths N/var/www/mission/venv/lib/python3.12/site-packages/setuptools/unicode_utils.py decomposer sr$$$UD11 {{7#$$UD1{{7# K   K s8A"" A/.A/cRt|trtjd|S|S)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%2O P $&7 8 A668   s;6* 6366.B$B4 BB B Bcfgc |j|dy#t$r=tj|||j |j||YywxYw)zSame idea as :func:`_read_utf8_with_fallback`, but for the :meth:`RawConfigParser.read` method. This method may call ``cfg.clear()``. r r(r*N)r-rr.r/clear)r2r$r+s r_cfg_read_utf8_with_fallbackr5QsT3 ( 3  d>O P   123sAAAceZdZdZdZy)r.zZ `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___SUMMARY_DETAILSrrr.r.asH Hrr.)rr configparserrcompatrwarningsrrr rr#LOCALE_ENCODINGr r1r5r.r<rrrAs} (2  Q*;?:N:N 3 SV "8<7K7K 3  3 # 3  3 6r