-
Notifications
You must be signed in to change notification settings - Fork 835
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
packaging for python microservice wrapper #293
Comments
Hi, This looks great. We were planning on cleaning up the python code so this is very timely. Some points:
@jklaise was planned to work on python cleanup so we should all get together to discuss. |
@kalefranz We are planning a python package for the wrappers and client commands to make the whole process of wrapping images and testing live deployments easier. We will host this within the main seldon-core repo and are keen to make it installable from pip and conda. Would you like to connect on Slack to discuss your ideas? |
@kalefranz I've started work on the Python package, it would be great if you could review it, especially re. conda recipe: #306 |
Closing via #306. A release on PyPI to follow together with a new release of Seldon Core. A release on conda-forge to follow shortly after, opened an issue at #341 @kalefranz . |
* fix Read on closed Body * fix lint * add extra test
Hello,
I'm a maintainer on the conda project, and we're interested in having the python microservice wrapper code in this repo be packageable as a conda package. As it exists right now, without a proper
setup.py
python project configuration file, the package wouldn't be as clean as it otherwise could be. Would you be open to a pull request with some moderate refactoring that would make https://github.com/SeldonIO/seldon-core/tree/cac15ba/wrappers/python more easily distributed as a conda package (and also able to be distributed as standard package on PyPI)?I've got potential WIP code at https://github.com/kalefranz/seldon-python-microservice showing what the changes might look like. If you're open to it and have any thoughts, comments, or advice before I open the PR, happy to take the feedback early.
The text was updated successfully, but these errors were encountered: