
    +j                        d Z ddlZddlZddlZdZdZdej        v r@ej                            ej        ej        	                    d          dz                      Zej
                            d          r2ej                            ej
                            d                    Zes>er=ej                            e          r$dZej                            ed          Zej                            egej
                            d	d
                              ej                  z             ej
        d	<   eej
        d<    eej                  Zej                            edej        j         dej        j         d          Z ej        e           ej        ed         ej        de         z   ej        dd<   ej        e_        ee_         ede            dS dS dS dS )a  Activate venv for current interpreter:

Use `from vtk.web import venv` along one of the following
 - `--venv /path/to/venv/base` argument
 - environment variable `VTK_VENV=/path/to/venv/base`

This can be used when you must use an existing Python interpreter, not the venv bin/python.
    NFz--venv   VTK_VENVTbinPATH VIRTUAL_ENVz
lib/python.z/site-packageszVTK is using venv: )__doc__ossitesys	VENV_BASEVENV_LOADEDargvpathabspathindexenvirongetexistsjoinbin_dirpathsepsplitlenprev_lengthversion_infomajorminorpython_libs
addsitedirprefixreal_prefixprint     M/DATA/AppData/hermes/venv/lib/python3.11/site-packages/vtkmodules/web/venv.py<module>r(      s    
			  



	sx)A)AA)E FGGI:>>* <
z : :;;I -y -RW^^I%>%> -Kgll9e,,G'RZ^^FB5O5O5U5UVXV`5a5a)abbBJv )BJ}#ch--K',,y*vs7G7M*v*vPSP`Pf*v*v*vwwKDOK   (;<<(38AkM+BBCHQQQKjCOCJ	E
+	
+
+,,,,,- - - - - -r&   