Meet DSS user Ben Powis, Data Science Manager at UK retail company MandM Direct Read More

Python code environment - Custom

Level 3
Python code environment - Custom


Please, could you explain the use of Python code environment with the option 'Custom (lookup in PATH)' ?

- In which context to use it ?
- How to do the setup ? which information is expected for 'Python executable' field ?



1 Reply


[TL;DR]  The "Custom (lookup in PATH)" option is meant for very specific use cases when the normal mechanisms (Python X.x from PATH) don't work. It is rarely needed and we recommend using the normal mechanisms as much as possible.

Do not forget to install the corresponding Python version on the server, as DSS will not do that for you.

[More details]

There are a few options on this screen:

Screenshot 2020-04-21 at 12.15.59.png

The normal mechanisms expect the python executables to be in the PATH variable. To be more precise, the exact syntax we expect is "python2.7", "python3.5" or "python3.6". You can test it easily if you have server access by typing "python2.7" in your shell.

The "Custom (lookup in PATH)" option will require you to provide a full path to a Python executable or an alias which points to it. This can introduce some risks when you work across several DSS nodes, as the paths may differ.  When moving from Design to Automation or API nodes, DSS needs to be able to rebuild the code-env.

Finally, you will need to be very careful to use only supported Python versions. As of today, this does not include Python 3.7, which are currently qualifying.

Hope it helps,