Skip to content

Fix warning in usb2can #570

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

Merged
merged 4 commits into from
May 19, 2019
Merged

Fix warning in usb2can #570

merged 4 commits into from
May 19, 2019

Conversation

felixdivo
Copy link
Collaborator

@felixdivo felixdivo commented May 8, 2019

This PR removes this DeprecationWarning:

invalid escape sequence \c

Is this correct to do? It now is like this example.

Closes #576.

This PR removes [this `DeprecationWarning`](https://travis-ci.org/hardbyte/python-can/jobs/529939236#L473):

> invalid escape sequence \c

Is this correct to to? It now is like [this example](https://docs.microsoft.com/en-us/windows/desktop/wmisdk/swbemlocator-connectserver#examples).
@codecov
Copy link

codecov bot commented May 8, 2019

Codecov Report

Merging #570 into develop will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           develop     #570   +/-   ##
========================================
  Coverage    63.99%   63.99%           
========================================
  Files           63       63           
  Lines         5572     5572           
========================================
  Hits          3566     3566           
  Misses        2006     2006

@felixdivo
Copy link
Collaborator Author

This improves on #511. @acolomb is this change correct?

@acolomb
Copy link
Contributor

acolomb commented May 10, 2019

I haven't had a chance to test this yet. If all goes well I will check back next week.

@felixdivo
Copy link
Collaborator Author

@acolomb Did it work?

@acolomb
Copy link
Contributor

acolomb commented May 19, 2019

Sorry I didn't get a chance to test it yet. Way too much work just before a longer vacation... Will report when tested, but that might be a couple of weeks now.

@felixdivo
Copy link
Collaborator Author

I am pretty sure this is a correct fix. I'll merge this for now. Please report back if it breaks something.

@felixdivo felixdivo merged commit 2ddca4e into develop May 19, 2019
@felixdivo felixdivo deleted the felixdivo-patch-usb2can-warning branch May 19, 2019 20:47
@acolomb
Copy link
Contributor

acolomb commented Jun 24, 2019

So I tested this now with a real USB2CAN hardware device. Successfully opened the backend without specifying a serial number prefix, therefore the adapter was correctly autodetect even with this change.

Works as expected, sorry for the long delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Escaping warning in usb2can serial selector
3 participants