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

Improove robustness of IRC messages #264

Merged
merged 2 commits into from Jul 1, 2019
Merged

Conversation

spaceone
Copy link
Contributor

For python2 it's not really clear that one have to use unicode while IRC
is a byte protocol. This might end up in TypeError exceptions.
Now both is supported and automatically encoded in the specified
encoding.

For python2 it's not really clear that one have to use unicode while IRC
is a byte protocol. This might end up in TypeError exceptions.
Now both is supported and automatically encoded in the specified
encoding.
@codecov-io
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (master@ea5f4aa). Click here to learn what that means.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #264   +/-   ##
=========================================
  Coverage          ?   74.57%           
=========================================
  Files             ?       74           
  Lines             ?     6664           
  Branches          ?        0           
=========================================
  Hits              ?     4970           
  Misses            ?     1694           
  Partials          ?        0
Impacted Files Coverage Δ
circuits/protocols/irc/message.py 77.14% <100%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ea5f4aa...a303b10. Read the comment docs.

@prologic prologic merged commit fcc82e6 into master Jul 1, 2019
@spaceone spaceone deleted the improove-irc-robustness branch July 1, 2019 13:06
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

3 participants