-
Notifications
You must be signed in to change notification settings - Fork 4.7k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
[Bug Report] Conflict between msgpack 1.0.0 and the deprecated msgpack-python #3251
Comments
@wangwwno1 I tested this on a new machine and everything worked as expected when following the docs and installing The error did appear when i tried to install Edit: To fix this, uninstall the |
@ahmed-elsaharti |
@wangwwno1 it shouldn't matter (as far as the scope of Airsim goes) if either of those packages produces errors though as long as the one recommended in the docs works. If you're trying to make this work just for airsim i would recommend uninstalling the packages mentioned above and installing I'll also do some testing on one more machine to make sure the results are consistent. |
@ahmed-elsaharti
Since msgpack v1.0.0 they have set the default encoding to utf-8 so these arguments are no longer effective. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Bug report
What's the issue you encountered?
https://pypi.org/project/msgpack-python/
When users install both msgpack and airsim they will have both msgpack and msgpack-python installed, which conflict.
Edit: After further examination, I find that this issue is related to the
msgpack-rpc-python
.They have a PR to fix this msgpack-rpc/msgpack-rpc-python#23 but by 2020.12.18 it hasn't merge yet.
Settings
N/A
How can the issue be reproduced?
pip install msgpack==1.0.2
Note: install msgpack, NOT msgpack-python, and msgpack must be newer than 1.0.0 as they change the api in this version.Include full error message in text form
What's better than filing an issue? Filing a pull request :).
The text was updated successfully, but these errors were encountered: