o 0׾g @sdZddlmZddlZddlmZddlmZddlmZddl Z e fZ dZ e jZiZdad d Zd d Zd dZddZgZeZeZddlmZee eedZdS)z5gevent friendly implementations of builtin functions.)absolute_importN)RLock)imp_acquire_lock)imp_release_lockbuiltinsTcsTd}zt}Wn tyYnw|dur(t}fdd}t||t<|S)NcstddS)N)_g_import_lockspop)_nameY/var/www/html/backend_erp/backend_erp_env/lib/python3.10/site-packages/gevent/builtins.pycb6sz__module_lock..cb)rKeyErrorrweakrefref)r lockrr r r __module_lock&s  rcOs|rtt|dts|dd}tst|i|St|d}tz|z t|i|}W|n|wWt |St w)a __import__(name, globals=None, locals=None, fromlist=(), level=0) -> object Normally python protects imports against concurrency by doing some locking at the C level (at least, it does that in CPython). This function just wraps the normal __import__ functionality in a recursive lock, ensuring that we're protected against greenlet import concurrency as well. rN) issubclasstype_allowed_module_name_types__lock_imports_importrracquirereleaser)argskwargs module_lockresultr r r __import__=s  r cCsdadS)a Internal function, called when gevent needs to perform imports lazily, but does not know the state of the system. It may be impossible to take the import lock because there are no other running greenlets, for example. This causes a monkey-patched __import__ to avoid taking any locks. until the corresponding call to lock_imports. This should only be done for limited amounts of time and when the set of imports is statically known to be "safe". FNrr r r r _unlock_imports]s r"cCsdadS)NTr!r r r r _lock_importsmsr#) copy_globals)names_to_ignore)__doc__ __future__rr gevent.lockrgevent._compatrrr __gbuiltins__strr __target__r rrrrr"r#__implements____all__ gevent._utilr$globals __imports__r r r r s.