Crash when calling rosdep

[rotu]

Description

Setup fails to call rosdep

https://github.com/ros2/rmw_cyclonedds/runs/565850604?check_suite_focus=true

Expected Behavior

Rosdep succeeds.

Actual Behavior

Rosdep fails.

   Installing collected packages: distro, rospkg, rosdistro, rosdep, vcstool
  Successfully installed distro-1.5.0 rosdep-0.19.0 rosdistro-0.8.0 rospkg-1.2.4 vcstool-0.2.7
Invoking "python c:\python37\scripts\rosdep init"
  python c:\python37\scripts\rosdep init
  python: can't open file 'c:\python37\scripts\rosdep': [Errno 2] No such file or directory
##[error]The process 'python' failed with exit code 2

Additional context

I expect this is caused by ros-infrastructure/rosdep#656, and that calling rosdep as an executable will now work, instead of having to call python <path/to/script>.

[acarrillo]

+1, I also experienced this with a system-wide install on linux! From my builds:

bash -c ". /opt/ros/kinetic/setup.bash && python /usr/bin/rosdep update"
python: can't open file '/usr/bin/rosdep': [Errno 2] No such file or directory

[acarrillo]

@rotu you might want to make an issue here instead https://github.com/ros-infrastructure/rosdep/issues

[thomas-moulard]

Tentative fix here: #101

[thomas-moulard]

Fix is merged.

[rotu]

@acarrillo it’s the opposite. Rosdep was fixed which broke the workaround in this github action.

[rotu]

@thomas-moulard fix confirmed. Should I switch to use master or wait for release?

[thomas-moulard]

0.0.17 has just been released. Closing this issue. Thanks for reporting!