robot-python-projects

Standardize Python project structure by applying common patterns for build tooling, testing, linting, and type checking across all robot codebases. This ensures consistent project organization using pyproject.toml, pytest, ruff, and mypy configurations.

Use pyproject.toml with hatchling for build tooling, pytest for testing, ruff for linting, and mypy for type checking. These common patterns maintain consistency across api/, robot-server/, and hardware/ directories.

The Opentrons robot Python project ecosystem includes api/, robot-server/, hardware/, auth-server/, shared-data/, server-utils/, system-server/, update-server/, usb-bridge/, and g-code-testing/ directories for centralized development guidelines.

Yes, you can use these guidelines to start organizing a new robot Python project. Begin by creating a pyproject.toml with hatchling configuration and a small API module following the documented standard patterns.

Consistent build configurations streamline development, testing, and collaboration across multiple robot Python directories. Standardizing pyproject.toml, pytest, ruff, and mypy settings ensures new contributors can quickly locate and add features.

Yes, this skill covers type checking and testing setup for hardware-related Python projects. It applies mypy for type checking and pytest for testing across hardware/ and related tool directories to maintain code quality.