From 86a0067f2eb9c2da8f284a4f15e2f08cc4c8ae12 Mon Sep 17 00:00:00 2001 From: Dustin Spicuzza Date: Sun, 5 Oct 2025 00:27:26 -0400 Subject: [PATCH] Use per-season entrypoint name - Fixes #5 --- README.md | 2 +- robotpy/main.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f155aeb..194077f 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ How RobotPy subcommands are implemented When a user runs `robotpy` or `python -m robotpy`, they are presented with several subcommands. Each of these subcommands is implemented as a class -that is registered using python's entry point mechanism in the "robotpy" +that is registered using python's entry point mechanism in the "robotpy_cli.YEAR" group. The registered class must meet the following requirements: * The docstring of the class is used when the user does --help. The first diff --git a/robotpy/main.py b/robotpy/main.py index 0d290d0..86813c8 100644 --- a/robotpy/main.py +++ b/robotpy/main.py @@ -240,7 +240,7 @@ def main() -> typing.NoReturn: cmds: typing.List[typing.Tuple[str, typing.Any]] = [] - for entry_point in entry_points(group="robotpy"): + for entry_point in entry_points(group="robotpy_cli.2026"): try: cmd_class = entry_point.load() except Exception: