Excerpt |
---|
|
Usage patterns and constraints with ros2/launch |
...
In order of criticality...
...
Code Block |
---|
|
def generate_launch_description():
# ...
myenv = os.environ
myenv["PYTHONUNBUFFERED"] = "1"
# ...
launch_description.add_action(
launch_ros.actions.Node(
package='py_trees_ros_tutorials',
node_name=node_name,
node_executable=node_executable,
output='screen' # screen is awkward, it's after the fact
env=myenv
)
) |
Workaround 2: set the emulate_tty flag flag as directed in ros2/launch/issues/188
Code Block |
---|
|
sed -i 's/emulate_tty=False/emulate_tty=True/g' /opt/ros/dashing/lib/python3.6/site-packages/launch/actions/execute_process.py |
- Symlinks for installed python files → ros2/launch/issues/187
- Introspector failing if env is set → ros2/launch/issues/203
- Multi-Node fails, but with surprising behaviour → ros2/launch/issues/204
- Multi-Node launch support as a feature → ros2/launch/issues/205