The Anaconda documentation
states that Python 3.4 can be run from an Anaconda 2.7 installation
by creating and activating a Python 3.4 environment. However, you
cannot do this with embedded Python. Therefore, it is recommended
that you use the Python 3.5 installer for both Python 2.7 and 3.4.
When starting SAS Web
Application Server, do so from a
shell in which you have activated Python, thus enabling the process
to use Python. For example, when starting the server using a script
such as tcruntime-ctl.sh, do so from the shell in which you activated
Python, as described above.
A rich set of Python
packages is available, covering a wide variety of computing needs.
You might want to add some of these packages to your Python environment.
Note: Make sure nomkl has been
installed as the first package, as instructed in the previous sections.
When you add packages
to an Anaconda environment, the packages are placed in <your-environment-path>/lib/python3.4/site-packages
.
In order to use the Python scripts that these packages require, add
their locations to the PYTHONPATH environment variable.
If your Python script
imports your own .py files, you also must add their location to PYTHONPATH.
An example location might be .(dot).
Some packages include
a lib directory, which also needs to be added to PYTHONPATH.
Finally, you must add <your-environment-path>/lib/python3.4
to
PYTHONPATH.
Anaconda sets the environment
variable CONDA_PREFIX when you activate an environment and sets it
to the location where Anaconda stores any new Python packages that
you install (for example, the site-packages folder).
Here is an example of
the locations that you might set for PYTHONPATH, after adding packages
to your Python 3.4 environment for 64-bit Linux:
export SITE_PACKAGES=$CONDA_PREFIX/lib/python3.4/site-packages
export PYTHONPATH=.:$CONDA_PREFIX/lib/python3.4
export PYTHONPATH=$PYTHONPATH:$SITE_PACKAGES
export PYTHONPATH=$PYTHONPATH:$SITE_PACKAGES/numpy
export PYTHONPATH=$PYTHONPATH:$SITE_PACKAGES/numpy/lib