Skip to content

Commit 973fa82

Browse files
committed
DCO Remediation Commit for Samuel Babak <samuel.babak@sas.com>
I, Samuel Babak <samuel.babak@sas.com>, hereby add my Signed-off-by to this commit: e72465e Signed-off-by: Samuel Babak <samuel.babak@sas.com>
1 parent e72465e commit 973fa82

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

examples/pzmm_generate_requirements_json.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@
1919
"\n",
2020
"This notebook provides an example execution and assessment of the create_requirements_json() function added in python-sasctl v1.8.0. The aim of this function is help to create the instructions (aka the `requirements.json` file) for a lightweight Python container in SAS Model Manager. Lightweight here meaning that the container will only install the packages found in the model's pickle files and python scripts.\n",
2121
"\n",
22-
"Additionally, the create_requirements_json() function provides an optional parameter `create_requirements_txt` which when set to `True` will generate a requirements.txt file alongside the requirements.json file. By default this option is set to `False`. The requirements.txt file is specifically needed when deploying Python models to SAS Event Stream Processing, which requires this format for package installation in their environment. While SAS Model Manager continues to use the requirements.json format, adding the requirements.txt file ensures compatibility across both platforms. \n",
22+
"Additionally, the create_requirements_json() function provides an optional parameter `create_requirements_txt` which when set to `True` will generate a requirements.txt file alongside the requirements.json file. By default this option is set to `False`. The requirements.txt file is needed when deploying Python models to SAS Event Stream Processing, which requires this format for package installation in their environment. While SAS Model Manager continues to use the requirements.json format, adding the requirements.txt file ensures compatibility across both platforms. \n",
2323
"\n",
2424
"### **User Warnings**\n",
2525
"The methods utilized in this function can determine package dependencies and versions from provided scripts and pickle files, but there are some stipulations that need to be considered:\n",

0 commit comments

Comments
 (0)