ImportError: No module named 'rospy'
Asked Answered
H

3

7

I installed the ROS package for Crazyflie, I wanted to run a simple script but when I type sudo python3 execute_trajectory.py , it gives me an error of no module named rospy.

This is the package: https://github.com/whoenig/crazyflie_ros and the file is in crazyflie_demo/scripts. Also I'm using Ubuntu 16.04 and ROS Kinect and I tried to run a Python3 script without ROS and everything works well.

This is my CMakeLists.txt

cmake_minimum_required(VERSION 2.8.3)
project(crazyflie_demo)

## Find catkin macros and libraries
## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz)
## is used, also find other catkin packages
find_package(catkin REQUIRED COMPONENTS
  roscpp
)

## System dependencies are found with CMake's conventions
# find_package(Boost REQUIRED COMPONENTS system)


## Uncomment this if the package has a setup.py. This macro ensures
## modules and global scripts declared therein get installed
## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html
# catkin_python_setup()

################################################
## Declare ROS messages, services and actions ##
################################################

## To declare and build messages, services or actions from within this
## package, follow these steps:
## * Let MSG_DEP_SET be the set of packages whose message types you use in
##   your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...).
## * In the file package.xml:
##   * add a build_depend and a run_depend tag for each package in MSG_DEP_SET
##   * If MSG_DEP_SET isn't empty the following dependencies might have been
##     pulled in transitively but can be declared for certainty nonetheless:
##     * add a build_depend tag for "message_generation"
##     * add a run_depend tag for "message_runtime"
## * In this file (CMakeLists.txt):
##   * add "message_generation" and every package in MSG_DEP_SET to
##     find_package(catkin REQUIRED COMPONENTS ...)
##   * add "message_runtime" and every package in MSG_DEP_SET to
##     catkin_package(CATKIN_DEPENDS ...)
##   * uncomment the add_*_files sections below as needed
##     and list every .msg/.srv/.action file to be processed
##   * uncomment the generate_messages entry below
##   * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...)

## Generate messages in the 'msg' folder
# add_message_files(
#   FILES
#   Message1.msg
#   Message2.msg
# )

## Generate services in the 'srv' folder
# add_service_files(
#   FILES
#   Service1.srv
#   Service2.srv
# )

## Generate actions in the 'action' folder
# add_action_files(
#   FILES
#   Action1.action
#   Action2.action
# )

## Generate added messages and services with any dependencies listed here
# generate_messages(
#   DEPENDENCIES
#   std_msgs  # Or other packages containing msgs
# )

###################################
## catkin specific configuration ##
###################################
## The catkin_package macro generates cmake config files for your package
## Declare things to be passed to dependent projects
## INCLUDE_DIRS: uncomment this if you package contains header files
## LIBRARIES: libraries you create in this project that dependent projects also need
## CATKIN_DEPENDS: catkin_packages dependent projects also need
## DEPENDS: system dependencies of this project that dependent projects also need
catkin_package(
#  INCLUDE_DIRS include
#  LIBRARIES crazyflie_demo
 CATKIN_DEPENDS roscpp
#  DEPENDS system_lib
)

###########
## Build ##
###########

## Specify additional locations of header files
## Your package locations should be listed before other locations
include_directories(
  ${catkin_INCLUDE_DIRS}
)

## Declare a cpp library
# add_library(crazyflie_demo
#   src/${PROJECT_NAME}/crazyflie_demo.cpp
# )

# Declare a cpp executable
add_executable(quadrotor_teleop src/quadrotor_teleop.cpp)

## Add cmake target dependencies of the executable/library
## as an example, message headers may need to be generated before nodes
# add_dependencies(crazyflie_demo_node crazyflie_demo_generate_messages_cpp)

# Specify libraries to link a library or executable target against
target_link_libraries(quadrotor_teleop
  ${catkin_LIBRARIES}
)

#############
## Install ##
#############

# all install targets should use catkin DESTINATION variables
# See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html

## Mark executable scripts (Python etc.) for installation
## in contrast to setup.py, you can choose the destination
# install(PROGRAMS
#   scripts/my_python_script
#   DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
# )

## Mark executables and/or libraries for installation
# install(TARGETS crazyflie_demo crazyflie_demo_node
#   ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
#   LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
#   RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
# )

## Mark cpp header files for installation
# install(DIRECTORY include/${PROJECT_NAME}/
#   DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION}
#   FILES_MATCHING PATTERN "*.h"
#   PATTERN ".svn" EXCLUDE
# )

## Mark other files for installation (e.g. launch and bag files, etc.)
# install(FILES
#   # myfile1
#   # myfile2
#   DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
# )

#############
## Testing ##
#############

## Add gtest based cpp test target and link libraries
# catkin_add_gtest(${PROJECT_NAME}-test test/test_crazyflie_demo.cpp)
# if(TARGET ${PROJECT_NAME}-test)
#   target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME})
# endif()

## Add folders to be run by python nosetests
# catkin_add_nosetests(test)

Any suggestions?

Thank you

Hyatt answered 10/8, 2018 at 16:16 Comment(2)
Everywhere in the CMakeLists.txt, you should have rospy instead of roscppDuenas
If your problem solved by my answer, consider please the vote up to it :)Hamlani
H
1

You shouldn't use from python3 because ROS Python version is 2.7, so use the following method to run a ros-node file:

rosrun <package-name> <node-name>

Define ROS kinetic to use python3 instead of python2.7 Link

I suggest read the crazyfile_ros readme in the installation section:

Installation

Clone the package into your catkin workspace:

git clone https://github.com/whoenig/crazyflie_ros.git
cd crazyflie_ros
git submodule init
git submodule update

Use catkin_make on your workspace to compile.


Run

rosrun crazyfile_demo execute_trajectory.py

Or use the corresponding launchfile in the creazyfile_demo package.


[NOTE]:

  • Make sure your .py file is executable (chmod +x execute_trajectory.py)
  • ros-python version is 2.7
Hamlani answered 14/8, 2018 at 20:39 Comment(1)
I prefer answer below by @LisaJiang, because I am using Python3 with ROS without issue, and my problem was solved by sourcing the devel in my docker containerFotina
N
10

In the current terminal, activate ROS

source /opt/ros/kinetic/setup.bash
Nadanadab answered 13/9, 2019 at 14:45 Comment(0)
H
1

You shouldn't use from python3 because ROS Python version is 2.7, so use the following method to run a ros-node file:

rosrun <package-name> <node-name>

Define ROS kinetic to use python3 instead of python2.7 Link

I suggest read the crazyfile_ros readme in the installation section:

Installation

Clone the package into your catkin workspace:

git clone https://github.com/whoenig/crazyflie_ros.git
cd crazyflie_ros
git submodule init
git submodule update

Use catkin_make on your workspace to compile.


Run

rosrun crazyfile_demo execute_trajectory.py

Or use the corresponding launchfile in the creazyfile_demo package.


[NOTE]:

  • Make sure your .py file is executable (chmod +x execute_trajectory.py)
  • ros-python version is 2.7
Hamlani answered 14/8, 2018 at 20:39 Comment(1)
I prefer answer below by @LisaJiang, because I am using Python3 with ROS without issue, and my problem was solved by sourcing the devel in my docker containerFotina
D
-1

I guess you have more than one version of python, so you install rospy in another version ans try to use it in this version. I suggest to try pip3 for installing package in python3.

Dignity answered 10/8, 2018 at 20:28 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.