requirements.txt file in the top level Cortex project directory (i.e. the directory which contains cortex.yaml):pip.conf inside the same directory as requirements.txt, and add the following contents:requirements.txt which are found in the private index.requirements.txt. Here's an example for GitHub:setup.py that describes your project's modules. Here's an example directory structure:requirements.txt will have this form:conda-packages.txt file in the top level Cortex project directory (i.e. the directory which contains cortex.yaml):conda-packages.txt file follows the format of conda list --export. Each line of conda-packages.txt should follow this pattern: [channel::]package[=version[=buildid]].conda-packages.txt:requirements.txt and conda-packages.txt are provided, Cortex installs Conda packages in conda-packages.txt followed by PyPI packages in requirements.txt. Conda and Pip package managers install packages and dependencies independently. You may run into situations where Conda and pip package managers install different versions of the same package because they install and resolve dependencies independently from one another. To resolve package version conflicts, it may be in your best interest to specify their exact versions in conda-packages.txt.3.6.9. Updating Python to a different version is possible with Conda, but there are no guarantees that Cortex's web server will continue functioning correctly. If there's a change in Python's version, the necessary core packages for the web server will be reinstalled. If you are using a custom base image, any other Python packages that are built in to the image won't be accessible at runtime.