Skip to content
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

Closed
jklaise opened this issue Dec 12, 2018 · 5 comments
Closed

S2I builder images should have pinned Python dependencies #340

jklaise opened this issue Dec 12, 2018 · 5 comments

Comments

@jklaise
Copy link
Contributor

jklaise commented Dec 12, 2018

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.

@JoelH96
Copy link
Contributor

JoelH96 commented Nov 29, 2019

#1160

@RafalSkolasinski
Copy link
Contributor

@JoelH96 @jklaise I think this issue can be already closed or there is something still missing?

@jklaise
Copy link
Contributor Author

jklaise commented Jan 14, 2020

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 seldon-core itself depends on which the merged PR does not address, however I don't recall why I wanted this now.

On a related note, now that 1.0 is out, the seldon-core version should be updated in the requirements.txt.

@RafalSkolasinski
Copy link
Contributor

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)

@RafalSkolasinski
Copy link
Contributor

Looking at the initial scope and changes introduced in #1160 I believe this one is closed.
We should open a new issue if there are any unpinned dependencies somewhere else.

Closing.

agrski pushed a commit that referenced this issue Dec 2, 2022
* fix trigger joins

* remove unused imports
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants