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

Announce zhinst-toolkit 1.0 #293

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Announce zhinst-toolkit 1.0 #293

wants to merge 3 commits into from

Conversation

fabiorossetto
Copy link
Collaborator

Description:
zhinst-toolkit has been stable since version 0.3 and we intend to keep that stability going forward. This is way we have decided to promote the library to version 1.0.

Despite the major version bump, this new version does not introduce any breaking change with respect to 0.7. Users can safely upgrade from 0.x to 1.0.

Even if we haven't changed the public interface, there are some differences you should be aware of:

  • Set operations always block until the value has been set on the device, regardless of the value of the deep flag. The deep flag is still available and can be useful if you want to get back the node value after the setting has been applied.

This PR also changes the documentation to better reflect the actual behavior of the deep flag.

Fixes issue: #

Checklist:

  • Add tests for the change to show correct behavior.
  • Add or update relevant docs, code and examples.
  • Update CHANGELOG.rst with relevant information and add the issue number.
  • Add .. versionchanged:: where necessary.

Fabio Rossetto added 2 commits February 7, 2025 11:45
Adjust the documentation of the deep flag to better reflect the behavior
in zhinst-toolkit 1.0.
We decided to bump toolkit to version 1.0. The public interface has been
stable for a while and we are committed to keep it so moving forward.

This version bump does *not* come with breaking changes in the public
interface. Ugprade from 0.x to 1.0 is safe.
@@ -66,8 +66,7 @@
"""

# Required for typing
def __init__(self, *args, **kwargs):
...
def __init__(self, *args, **kwargs): ...

Check notice

Code scanning / CodeQL

Statement has no effect Note

This statement has no effect.
25.04 changes the behavior of `set` to be fully blocking until device
acknowledgement. To have the same behavior in toolkit, the zhinst.core
requirement has been bumped.
@fabiorossetto fabiorossetto force-pushed the fabior/deep_doc branch 2 times, most recently from 07895f0 to eae8e48 Compare February 7, 2025 12:42
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

Successfully merging this pull request may close these issues.

1 participant