You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 21, 2024. It is now read-only.
We want python-pachyderm to support both v2.x and v1.x of mainline pachyderm, and in general, we want to support one backward version in addition to the most current version of mainline pachyderm, so vX.y and vX-1.y. This would give us the ability to release API breaking changes to python-pachyderm without locking major versions of python-pachyderm to major versions of mainline pachyderm.
To achieve this goal, we need the following:
ability to generate proto library code for both versions
separate execution paths to use different versions
One possibility to specify API version could involve something like:
In the future, we could package up the protos as a separate Python package deployed on PyPI, and remove the generated code from this repo.
NOTE:
After some experimentation, it seems like we can import one version of the protos but not both at the same time. This should be acceptable behavior given that we do not expect the users to be interacting with multiple pachyderm clusters via the same python instance. However, if this is a false assumption, then we need to re-visit this design.
The text was updated successfully, but these errors were encountered:
We want python-pachyderm to support both
v2.x
andv1.x
of mainline pachyderm, and in general, we want to support one backward version in addition to the most current version of mainline pachyderm, sovX.y
andvX-1.y
. This would give us the ability to release API breaking changes to python-pachyderm without locking major versions of python-pachyderm to major versions of mainline pachyderm.To achieve this goal, we need the following:
One possibility to specify API version could involve something like:
Behind the scenes, we would separate the two versions using different directories:
In the future, we could package up the protos as a separate Python package deployed on PyPI, and remove the generated code from this repo.
NOTE:
The text was updated successfully, but these errors were encountered: