Tracking locally, privately built Python libraries
Now, let's turn our attention to tracking locally, privately built Python libraries. For publicly released Python libraries, we can explicitly specify their released version, which is published in PyPI, in a requirements file or a conda.yaml
file. For example, this chapter's conda.yaml
file (https://github.com/PacktPublishing/Practical-Deep-Learning-at-Scale-with-MLFlow/blob/main/chapter04/conda.yaml) defines the Python version and provides a reference to a requirements file, as follows:
name: dl_model
channels:
- conda-forge
dependencies:
- python=3.8.10
- pip
- pip:
- -r requirements.txt
The Python version is defined as 3.8.10
and is being enforced. This conda.yaml
file also refers to a requirements.txt
file, which contains the following versioned Python packages as a requirements.txt
file, which is located in the same directory...