Re: pyDevSup and PyDevice: Virtual Environment

[Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>]

On 4/26/22 02:43, Kuldeep Joshi wrote:
>  > for pyDevSup, any suggestions as to how I can automate switching to the virtual environment before invoking the IOC?? (source ~/myvirtEnv/bin/activate??? at the start of st.cmd file??)
>
>
>     All the 'activate' script does these days is modify $PATH so yoy
>     can instead directly reference 'bin/python` in a virtualenv.
>
>      > /path/to/env/bin/python myscript.py
>
> How do I point the path to the virtual environment so that the IOC can use it.
If practical, (re)build pyDevSup against that specific interpreter.

> make PYTHON=/path/to/env/bin/python
Alternately, if you are certain that the ABI versions match, you can
add $(TOP)/python$(PY_VER) to $PYTHONPATH and "import devsup".  The
"softIocPy*" executable isn't as special as it used to be.  For an
example run:

> make ipython
which is a shortcut to run an ipython shell with $PYTHONPATH set
appropriately to for the $PYTHON used.


Also, I will mention

https://dls-controls.github.io/pythonSoftIOC/master/index.html

as possible an alternative which fits better into the python
ecosystem (cf. "pip install softioc").


> W.R.T.
>
> #!../../bin/linux-x86_64/softIocPy2.7
> # Interpreter not started
> dbLoadDatabase("../../dbd/softIocPy.dbd",0,0)
> softIocPy_registerRecordDeviceDriver(pdbbase)
> # Interpreter started
>
>     or
>
>      > #!/path/to/env/bin/python
>      > ...
>
> How do I do it while invoking the IOC, with st.cmd file where it is the #!/path/points/to/the/softioc
>
> I am presently having another bash script file from which I activate the the virtual environment and invoking the st.cmd file