PyKitOps is a community favorite, and for good reason. It works with the tools your data scientists rely on like Project Jupyter, MLflow, and Weights & Biases creating ModelKit ‘snapshots’ as they work. Because their work is already packaged as an open source standardized artifact, it can be handed off to the ML devs and DevOps team without any further packaging. Why does this matter? ModelKits create a single artifact that spans the full ML lifecycle, it contains the full project history. Compare that to a workflow where the project is repackaged into proprietary formats as it moves from team to team. Not only is it a pain, but a lot of the history is lost.
PyKitOps 1.4 is out for my #python lovers. It adds the ability to interact with remote registries to: * Get the kitfile without pulling the whole ModelKit - a great way to check the contents, especially if you want to grab only the model, or just the dataset * Inspect the ModelKit's manifest to check artifact sizes or signing * Delete a remote ModelKit Grab it with pip. You can learn more about PyKitOps from our docs: https://lnkd.in/eF6CdJhj