-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S2I builder images should have pinned Python dependencies #340
Comments
I don't quite remember the context of this, but I think it may have been to do with having pinned versions of packages that On a related note, now that 1.0 is out, the |
Seldon-core itself dependencies are listed in the setup.py under install_requires. Good point about the seldon-core version in requirements.txt. Though, I am not sure where that is actually used as latest image from docker hub seems to use 1.0 installed from sources: satriani ➜ ~ docker run --rm -it seldonio/seldon-core-s2i-python37:0.15 bash
root@11dab7628ff1:/microservice# pip freeze | grep seldon
# Editable install with no version control (seldon-core==1.0.0) |
Looking at the initial scope and changes introduced in #1160 I believe this one is closed. Closing. |
* fix trigger joins * remove unused imports
Currently S2I builder images use "pip install seldon-core" or the local equivalent to install the seldon-core Python package and its dependencies, we should specify to use the requirements.txt for pinned package versions.
The text was updated successfully, but these errors were encountered: