Fix Python wrapper for peek functions #127
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…not allowing a read of the message.
|
If someone else says that these changes work I'd merge them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated the Python wrapper for the expanded peek functionality from #106.
Original peek function in the wrapper function has had the
uint_16tadded in the type definition. Also, the expanded functionality introduced in #106 has been added to a second Python function.Has been tested with various calls to the peek function to verify that any implementation of peek prior to #106 will still work with the addition to allow for the expanded functionality. Also, tested new calls of the peek to verify that they do call the two separate peek functions.