Metadata-Version: 2.4
Name: play_launch
Version: 0.17.0
Summary: ROS 2 launch inspection tool. Install with your ROS distribution as an extra: pip install "play_launch[jazzy]"
Author-email: "Lin, Hsiang-Jui" <jerry73204@gmail.com>
License-Expression: BSD-3-Clause
Project-URL: Repository, https://github.com/NEWSLabNTU/play_launch
Keywords: ros2,launch,profiling,monitoring,robotics
Classifier: Development Status :: 4 - Beta
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python :: 3
Requires-Python: >=3.10
Description-Content-Type: text/markdown
Provides-Extra: humble
Requires-Dist: play_launch_humble==0.17.0; extra == "humble"
Provides-Extra: jazzy
Requires-Dist: play_launch_jazzy==0.17.0; extra == "jazzy"
Provides-Extra: kilted
Requires-Dist: play_launch_kilted==0.17.0; extra == "kilted"
Provides-Extra: lyrical
Requires-Dist: play_launch_lyrical==0.17.0; extra == "lyrical"
Provides-Extra: rolling
Requires-Dist: play_launch_rolling==0.17.0; extra == "rolling"

# play_launch

Resolve, run and analyze ROS 2 launch executions, with resource monitoring
and a web UI. See the [repository](https://github.com/NEWSLabNTU/play_launch).

play_launch is built against one ROS 2 distribution, whose libraries it
uses at run time. Install it with yours as an extra:

```bash
pip install "play_launch[${ROS_DISTRO}]"     # humble, jazzy, kilted, lyrical, rolling
```

This package has no code: the extra pulls `play_launch_<distro>`, which
provides the `play_launch` command. A plain `pip install play_launch`
installs nothing usable. The `rolling` build matches Rolling as of the
release; Rolling changes, so rebuild from source if it stops loading.
