Migrate plugins - Githubissues

superduper-io / superduper

Superduper: Integrate AI models and machine learning workflows with your database to implement custom AI applications, without moving your data. Including streaming inference, scalable model hosting, training and vector search.

Apache License 2.0

4.71k stars 460 forks source link

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?

[ ] Did you run make unit_testing and make integration-testing successfully?

[ ] Do new classes, functions, methods and parameters all have docstrings?

[ ] Were existing docstrings updated, if necessary?

[ ] Was external documentation updated, if necessary?

What shall we do with "core" plugins/ extensions, for example ext/numpy? Shouldn't we move this somehow? Also, what is the plan for moving away from the superduper.ext.* sub-packages? Shall we raise a warning which can become an error later?

We need to retain some core plugins, which are pre-set, and can continue to use this ext until a better name is found.

I added the warning, and I think we can directly remove those plugins in the next one or two versions, at which point an import error will be thrown.

superduper-io / superduper

Migrate plugins #2378

Description

Related Issues

Checklist

Additional Notes or Comments