(ph=pSrSSKrSSKr\RS:rSr\"\S5rSrSr Sr S r S S jr g) z Support functions for dealing with differences in platforms, including Python versions and implementations. This file should have no imports from the rest of zope.interface because it is used during early bootstrapping. N)c[U[5(a [US5n[U[5(aU$[S5e)Nasciiz)name must be a string or ASCII-only bytes) isinstancebytesstr TypeError)names I/var/www/html/venv/lib/python3.13/site-packages/zope/interface/_compat.py_normalize_namer s9$4!$ ? @@pypy_version_infocN[RRS5nUS:HnU$)z Return a true value if the C optimizations are required. This uses the ``PURE_PYTHON`` variable as documented in `_use_c_impl`. PURE_PYTHON0osenvironget)pure_env require_cs r _c_optimizations_requiredr's% zz~~m,HCI rc\[5(aSO[4nSSKJn U$!Ua gf=f)z Return the C optimization module, if available, otherwise a false value. If the optimizations are required but not available, this raises the ImportError. This does not say whether they should be used or not. r)_zope_interface_coptimizationsF)r ImportErrorzope.interfacer)catchc_opts r _c_optimizations_availabler!2s4,--BK>EJ s "++c`[RRS5nUSL=(a US:g$)z. The opposite of `_c_optimizations_required`. rNrr)rs r _c_optimizations_ignoredr#Ds*zz~~m,H 4  3HO3rcp[[S5n[5(agU(ag[5(+$)z Return a true value if we should attempt to use the C optimizations. This takes into account whether we're on PyPy and the value of the ``PURE_PYTHON`` environment variable, as defined in `_use_c_impl`. rTF)hasattrsysrr#)is_pypys r _should_attempt_c_optimizationsr(Ls/c./G ""') ))rc^^T=(d TRmU=(d [R"S5RnUU4SjnU"5nTUTS-'TUTS-'U$)a Decorator. Given an object implemented in Python, with a name like ``Foo``, import the corresponding C implementation from ``zope.interface._zope_interface_coptimizations`` with the name ``Foo`` and use it instead. If the ``PURE_PYTHON`` environment variable is set to any value other than ``"0"``, or we're on PyPy, ignore the C implementation and return the Python version. If the C implementation cannot be imported, return the Python version. If ``PURE_PYTHON`` is set to 0, *require* the C implementation (let the ImportError propagate); note that PyPy can import the C implementation in this case (and all tests pass). In all cases, the Python version is kept available. in the module globals with the name ``FooPy`` and the name ``FooFallback`` (both conventions have been used; the C implementation of some functions looks for the ``Fallback`` version, as do some of the Sphinx documents). Example:: @_use_c_impl class Foo(object): ... ch>[5(dT$[5nU(dT$Un[UT5$)N)r(r!getattr)r __traceback_info__r py_impls r find_impl_use_c_impl..find_implzs4.00N*,N"ud##rPyFallback)__name__r& _getframe f_globals)r.r globsr/c_impls`` r _use_c_implr8\s`6  #7##D  /S]]1%//E $[F!E$+&E$  Mr)NN) __doc__rr& version_infoPY313_OR_OLDERr r%PYPYrr!r#r(r8rrr r=sR !!G+As'($4 * /r