fixing datetime call in tools/zbfind - #165
Merged
Merged
Conversation
and some whitespace
zigbee_crypt: fix memory leak
Contributor
|
@SrEdeu upon merging this I looked and realized this appears to not work on Python 2.7 at least: Which version are you on that you see issues with the way it was done? Can you send similar output as to the above? |
rmspeers
pushed a commit
that referenced
this pull request
Mar 24, 2019
… correct on Python 2.7, updated dates in README
Contributor
Author
|
@rmspeers I'm also working on Python 2.7, and having same outputs as you. I assumed that it was because datetime was imported as |
SteveJM
pushed a commit
to SteveJM/killerbee
that referenced
this pull request
Jan 16, 2020
… do not test correct on Python 2.7, updated dates in README
This file contains hidden or 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
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.
No description provided.