-
Notifications
You must be signed in to change notification settings - Fork 405
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
ModuleNotFoundError: No module named 'termios' #27
Comments
Hrm... if the termios python library isn't available on Windows, then it will either need to be made optional or replaced with an equivalent python library for Linux. termiwin is a C library, so it can't be used. I've made a branch named Here's the teleop_twist_keyboard.py on that branch: https://github.com/ros-teleop/teleop_twist_keyboard/blob/optional_termios/teleop_twist_keyboard.py and here is the diff showing the changes that I made: https://github.com/ros-teleop/teleop_twist_keyboard/compare/optional_termios I don't have windows or the time to test this, but if you are able to confirm that it works for you or update teleop_twist_keyboard and submit a PR which makes it work on Windows, I will gladly accept those changes and release a new version. Good luck! |
@trainman419 I wasn't able to get complete replacement for termios and tty but i found msvcrt a good replacement, it records a new key input every time, it is working fine for me but don't weather the code is capable of publishing here it is. from future import print_function import threading import roslib; roslib.load_manifest('teleop_twist_keyboard') from geometry_msgs.msg import Twist have_msvcrt = False msg = """
|
Nice work! |
I am using ros on windows (not on wsl ) and want to use teleop twist keyboard package to control the robot, and it is showing error ModuleNotFoundError: No module named 'termios' i searched on google and found that termios in not for windows so what can do to solve this problem, also while searching online i found termiwin, should I use that, if yes how
The text was updated successfully, but these errors were encountered: