Skip to content

Conversation

@karlding
Copy link
Collaborator

In Python 2, the str type was used for text and bytes, whereas in Python
3, these are separate and incompatible types. This broke instantiation
of a VectorBus when the app_name parameter in init was set to None.

This correctly sets it to a bytes object.

Fixes #796

In Python 2, the str type was used for text and bytes, whereas in Python
3, these are separate and incompatible types. This broke instantiation
of a VectorBus when the app_name parameter in __init__ was set to None.

This correctly sets it to a bytes object.

Fixes hardbyte#796
@karlding karlding mentioned this pull request Apr 19, 2020
@codecov
Copy link

codecov bot commented Apr 19, 2020

Codecov Report

Merging #814 into develop will increase coverage by 2.70%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #814      +/-   ##
===========================================
+ Coverage    67.00%   69.71%   +2.70%     
===========================================
  Files           70       70              
  Lines         6577     6577              
===========================================
+ Hits          4407     4585     +178     
+ Misses        2170     1992     -178     

@hardbyte hardbyte merged commit 8c1b3f3 into hardbyte:develop Apr 19, 2020
@karlding karlding deleted the issue_796_fix_vector_interface_python3_bytes_string branch May 4, 2020 07:04
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.

Type error on vector CANlib

2 participants