-
Notifications
You must be signed in to change notification settings - Fork 636
canplayer in setup.py clashes with can-utils #162
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
Comments
What should it be named instead? Maybe canlogplayer? |
what about |
What about removing the scripts and just having them as modules?
|
I personally prefer that way since I have control over which interpreter is used. But it is harder to remember. |
hardbyte
added a commit
that referenced
this issue
May 31, 2017
hardbyte
added a commit
that referenced
this issue
Jun 16, 2017
hardbyte
added a commit
that referenced
this issue
Jun 16, 2017
hardbyte
added a commit
that referenced
this issue
Jun 16, 2017
boris-wenzlaff
pushed a commit
to boris-wenzlaff/python-can
that referenced
this issue
Mar 23, 2018
boris-wenzlaff
pushed a commit
to boris-wenzlaff/python-can
that referenced
this issue
Mar 23, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The Linux
can-utils
package already has acanplayer
binary which clashes with thecanplayer
entry point in the latestsetup.py
.Trying to compile my yocto image results in the following error:
Removing it from
setup.py
resolves the problem.The text was updated successfully, but these errors were encountered: