search

Materials-Consortia / optimade-python-tools

Tools for implementing and consuming OPTIMADE APIs in Python
https://www.optimade.org/optimade-python-tools/
MIT License
71 stars 44 forks source link

Versioning models independently of this package #609

Open ml-evs opened 4 years ago

ml-evs commented 4 years ago

Following the comments around maintaining two parallel releases of the specification, we should have a discussion about how we want to version our models in the future.

Is the API stable enough to be able to pluck the models out into a separate repository where they can be versioned as releases, or does this add too much overhead on what will hopefully be fairly static objects? [additionally two model versions could not be used simultaneously with this approach]

Should we explicitly add logic for versioning models in this package, e.g. extend OptimadeField to include some kind of "supported versions" attribute per field, so that different implementations can be validated (for example) with different model versions?

Paraphrased from post by @ml-evs in https://github.com/Materials-Consortia/optimade-python-tools/issues/593#issuecomment-731199620

shyamd commented 3 years ago

This is another reason to switch to namespace packages. To have a single repo with multiple packages in it.