Skip to content

Use per-season entrypoint name #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 9, 2025
Merged

Use per-season entrypoint name #10

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion robotpy/main.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down