-
Notifications
You must be signed in to change notification settings - Fork 13
Installation
All production/test servers have been migrated to python 3, and some installation/deployment part are managed by puppet.
Make sure the node has python3. If not, try yum install python3
.
And,
python3 -m venv /opt/jedi_python
. /opt/jedi_python/bin/activate
pip install --upgrade pip panda-server
One needs to follow the updates of panda-server for this.
If one needs to test with other branch than master of panda server, run the following instead:
pip install git+https://github.com/PanDAWMS/panda-server.git@flin
where flin
above can be replaced with the name of other branch to test.
pip install git+https://github.com/PanDAWMS/panda-jedi.git
Or with a specific branch if necessary:
pip install git+https://github.com/PanDAWMS/panda-jedi.git@python3
where python3
above can be replaced with the name of other branch to test.
Configure panda server and jedi the same way as on prod servers.
Just note that ${VIRTUAL_VENV}
should be used in every line (e.g. in sysconfig conifgs) where python executable will be called.
First of all, make sure the venv is activated:
. /opt/jedi_python/bin/activate
Next, source sysconfig env of panda server and jedi:
. /etc/sysconfig/panda_server
. /etc/sysconfig/panda_jedi
Then one can go on following steps in JEDI-test-scripts .
!! Note the path of test scripts could be different due to the venv !!