Customization and environment configuration

Follow these instructions for customizing and configuring the environment of IBM® Open Enterprise SDK for Python.

IBM Open Enterprise SDK for Python requires /usr/bin/env, but your system might only have /bin/env. You can take the following steps to verify the path for the env command:

Ensure that /usr/bin/env exists and provides a correct listing of the environment. In an SSH or Telnet shell environment, run the following command to verify the location and contents of env. The command returns a list of name and value pairs for the environment in your shell.
```
/usr/bin/env
```
If /usr/bin/env does not exist, complete the following steps to set it up:
1. Locate the env program on your system. A potential location is /bin/env.
2. Create a symbolic link (symlink) so that /usr/bin/env resolves to the true location of env. For example:
```
ln -s /bin/env /usr/bin/env
```
3. In an SSH or Telnet shell environment, run the following command to verify if the symlink works. The command returns a list of name and value pairs for the environment in your shell.
```
/usr/bin/env
```
Verify that the symbolic link for the env command persists across system IPLs.
Depending on how /usr/bin/ is configured on your system, the symbolic link for /usr/bin/env might not persist across an IPL without extra setup. Ensure that your IPL setup includes creation of this symbolic link, if necessary.
If you intend to build or install packages using C or C++, see Using IBM C/C++ compilers with IBM Open Enterprise SDK for Python.

Optional: Set symlinks for /usr/bin. When using pip, some packages expect Python to be installed into /usr/bin. You can set symlinks by running the following commands:

ln -sf <install directory>/bin/python3 /usr/bin/python

ln -sf <install directory>/bin/python3 /usr/bin/python3

ln -sf <install directory>/bin/python3 /usr/bin/python3.13

Note that <install directory> in these examples is the path you chose for installation.