Skip to content
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

Versioning #12

Open
henrypinkard opened this issue Jun 28, 2024 · 1 comment
Open

Versioning #12

henrypinkard opened this issue Jun 28, 2024 · 1 comment

Comments

@henrypinkard
Copy link
Member

How should the versioning of pydevice work? What's the relationship between it and the device interface version in core? @marktsuchida I know you had some good insights on this

@marktsuchida
Copy link
Member

When the device interface version changes, the more common cases are adding a device type, adding member functions, or replacing existing member functions with equivalent functionality. The last type can usually be absorbed by PyDevice in its C++ code. When features are added, new Python devices will be able to use them but existing ones won't care.

The harder problem is the versioning between devices written in Python and the PyDevice adapter. In the long term, we'd want to be able to make some guarantees so that a range of PyDevice adapter versions work with a given version of Python device code. Hopefully we'll gain some experience with the types of things that need consideration while we're still in unstable-API mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants