Open
Conversation
|
I been waiting 3 moths for a pull request to be merge or rejected :( |
|
@foXes68 Let's make the project alive again. please check it out and do a pull request there if you found any bugs. |
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.
Seems like
self.serial.read(1)inserial_comms.pyreturns bytes in Python 3.x.But code expects strings and compares returned value with strings like
RX_EOL_SEQ = '\r\n'or ''. The comparison result will always beFalse.In this case
SerialCommswill never_handleLineReadandTimeoutExceptionwill be raised.