Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

robotpy-cli

New for 2024, this package is used to execute subcommands on a RobotPy project. This does not actually implement any subcommands itself, but provides a mechanism to execute those subcommands.

Usage

On Windows:

py -m robotpy

On Linux/macOS:

python -m robotpy

See the RobotPy documentation for more information.

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_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 line is treated as the summary, and all other lines are displayed when the subcommand specific help is queried.

If the subcommand is a group of commands:

  • The class must have a subcommands attribute, which is a list of (name, subcommand_class) tuples. The subcommand_class must meet the requirements for a subcommand.

If it is a subcommand that is executed:

  • The constructor must take a single argument, an argparse.ArgumentParser. The object may register any arguments or subparsers that it needs.
  • The run function is called when the subcommand is used by the user. The arguments to this function are passed in by name, and the names can be any of the options that the subcommand registered. A parameter without a corresponding registered option must have a default value; when the option is absent, Python uses that default. There are also these special argument names:
    • options - if specified, this is the Namespace returned by parse_args
    • robot_class - if specified, the user's robot.py will be loaded and it will be inspected for their robot class, which will be passed in as this option
    • load_robot_class - if specified, this is a function that will return the same object that robot_class would have returned. The robot class will not be loaded until the function is called. You may not specify robot_class and load_robot_class, and you should not call the function more than once.
    • main_file - if specified, the name of the user's robot.py file. This is not guaranteed to exist unless robot_class is also an option.
    • project_path - if specified, the name of the directory that contains the user's robot.py file. This is not guaranteed to exist unless robot_class is also an option.

Release files for robotpy-cli 2027.0.1b2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for robotpy-cli 2027.0.1b2
File Size Uploaded
robotpy_cli-2027.0.1b2.tar.gz 9.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for robotpy-cli 2027.0.1b2
File Interpreter ABI Platform
robotpy_cli-2027.0.1b2-py3-none-any.whl Python 3 none any Details

Total release size: 18.2 kB

Release files / robotpy_cli-2027.0.1b2.tar.gz

Download URL robotpy_cli-2027.0.1b2.tar.gz
Size 9.1 kB
Tags Source
SHA-256 checksum
How to use checksums
2700eec883a6bb834231f9cb44d9a6468f5f03edb11591ded5d01b27bce85ce9
BLAKE2b-256 checksum
How to use checksums
47c70cf1fcb47cb35523e3274f4d0dc04f696656d66dc7d9fcacade4b60b70d8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.

Transparency log

Release files / robotpy_cli-2027.0.1b2-py3-none-any.whl

Download URL robotpy_cli-2027.0.1b2-py3-none-any.whl
Size 9.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
84b76655702ea1b54e4d1b0eebef3792f1606c67e5b98bf7db0ce02af210eb31
BLAKE2b-256 checksum
How to use checksums
1547d371a02f11ba0830c42eb6d87720873410a27c26a90b8089d09ee7329916
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page