Initializing help system before first use

Developing a Python App on FICO® Platform

When developing a Python app for FICO® Platform, you must specify the versions of Python and any other necessary packages that must be installed on the Xpress Insight worker.

A CONDA environment.yml file must be used to define the version of Python to be installed on the Insight worker, but other package versions can be defined either within the environment.yml file, or within a pip requirements.txt file. Both the environment.yml file (and the requirements.txt file, if present) must be stored in the model_resources directory.

Note: After the specified packages have been installed, they will be cached per App per Worker. Packages will be fetched again if the environment.yml or requirements.txt files are changed.

When creating a python project using Xpress Workbench on FICO® Platform, the environment.yml file is created under model_resources.

If you upload a Python Xpress Insight application to FICO® Platform, the Python source is unzipped and placed in the model_resources directory. If the app does not contain an environment.yml file, a basic file will be created.

When developing on FICO® Platform, the Xpress Workbench terminal does not have access to Java or node.js

Creating the environment.yml and requirements.txt files

The environment.yml file should be created in the model_resources directory. To use the Xpress or Xpress Insight modules, the fico-xpress channel must be specified in the environment.yml file. The environment.yml file should take the following format: 

channels:
	- conda-forge
dependencies:
	- python=3.10
	- pip
	- pip:
		- xpress~=9.1.0
		- xpressinsight=1.6.0
By using the ~= notation with a package version, you will receive the latest minor version of the package within your specified major version. For example, if you specify xpress~=9.1.0 you will receive the latest 9.1.x version.
Note: Exact versions should be used for production applications. The exact version syntax varies between the pip: block (which is passed straight to the pip tool) and regular Conda version spec.

Conda uses single = for exact version match; pip uses ==. They both use the same ~= syntax for approximate matching.

To see the full specification of the environment.yml file, see the CONDA documentation.

Alternatively, to use pip to define packages to be installed, create a requirements.txt file in the model_resources directory, using the following format: 
xpress == 9.1
xpressinsight == 1.6.0
To see the full specification of the requirements.txt file, see the pip documentation.
Note: Please note that URLs cannot be included in either the environment.yml file or the requirements.txt file.
.
Covered Topics
Parent Topic Insight 5 Python Developer Guide

© 2001-2026 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.