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

Signal cleanup #171

Merged
merged 3 commits into from Aug 3, 2017
Merged

Signal cleanup #171

merged 3 commits into from Aug 3, 2017

Conversation

epage
Copy link
Contributor

@epage epage commented Aug 3, 2017

  • This contribution adheres to CONTRIBUTING.md.
  • New tests have been created for any new features or regression tests for bugfixes.
  • tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

Docs are improved as well.

BREAKING CHANGE: If named parameters were used with signal read/write,
then you'll need to update your code from `value_buffer` to `signals`.
Future signal reads will have a "number of values per signal", so having
"to read" in there is a bit much.

BREAKING CHANGE: For clients calling frame reads with keyword parameters,
`num_bytes_to_read` and `num_frames_to_read` are now `num_bytes` and
`num_frames`.
@coveralls
Copy link

coveralls commented Aug 3, 2017

Coverage Status

Coverage remained the same at 64.098% when pulling 326f3bb on epage:signal_cleanup into 458b2ec on ni:master.

@epage epage merged commit f87765f into ni:master Aug 3, 2017
@epage epage deleted the signal_cleanup branch August 3, 2017 21:38
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.

None yet

2 participants