B ` @s\ddlZddlmZGdddejZddZeedZdd Zdd d ZGd d d Z dS)N)global_registryc@s:eZdZd ddZddZeZddZdd Zd d ZdS) ThreadLocalManagerNcCsg|_||_dS)N)stackdefault)selfrr[/home/kop/projects/devel/pgwui/test_venv/lib/python3.7/site-packages/pyramid/threadlocal.py__init__szThreadLocalManager.__init__cCs|j|dS)N)rappend)rinforrrpushszThreadLocalManager.pushcCs|jr|jSdS)N)rpop)rrrrr szThreadLocalManager.popcCs(y |jdStk r"|SXdS)N)r IndexErrorr)rrrrgets zThreadLocalManager.getcCsg|jdd<dS)N)r)rrrrclearszThreadLocalManager.clear)N) __name__ __module__ __qualname__r r setr rrrrrrrs  rcCs dtdS)N)requestregistry)rrrrrdefaults#sr)rcCs tdS)a Return the currently active request or ``None`` if no request is currently active. This function should be used *extremely sparingly*, usually only in unit testing code. It's almost always usually a mistake to use ``get_current_request`` outside a testing context because its usage makes it possible to write code that can be neither easily tested nor scripted. r)managerrrrrrget_current_request*s rcCs tdS)a Return the currently active :term:`application registry` or the global application registry if no request is currently active. This function should be used *extremely sparingly*, usually only in unit testing code. It's almost always usually a mistake to use ``get_current_registry`` outside a testing context because its usage makes it possible to write code that can be neither easily tested nor scripted. r)rr)contextrrrget_current_registry9src@s4eZdZddZddZddZddZd d Zd S) RequestContextcCs ||_dS)N)r)rrrrrr KszRequestContext.__init__cCs |j}|j}t||d|S)N)rr)rrrr )rrrrrrbeginNszRequestContext.begincCs tdS)N)rr )rrrrendTszRequestContext.endcCs|S)N)r)rrrr __enter__WszRequestContext.__enter__cGs |dS)N)r)rargsrrr__exit__ZszRequestContext.__exit__N)rrrr rrr r"rrrrrJs r)N) threadingZpyramid.registryrlocalrrrrrrrrrrs