hatch-mojo

You can compile .mojo sources into Python extensions by configuring hatch-mojo as a build dependency in your pyproject.toml, which uses Hatchling build hooks to automate the compilation process and include the artifacts in the final wheel distribution.

Yes, Hatch build hooks support compiling Mojo code into Python extensions, executables, and libraries, managing compilation jobs and output artifact generation directly within the standard Hatchling build environment.

Integrating Mojo compilation into Python packaging is best handled by adding this build hook to your Hatchling configuration, which automates dependency management and compiles performance-critical Mojo components into the wheel.

Yes, this approach relies on Hatchling as the build backend, using custom build hooks to manage Mojo compilation jobs and generate the required Python extensions or libraries for the wheel distribution.

Compilation failures often stem from incorrect build dependency configuration in pyproject.toml, as this hook requires explicit declaration of compilation jobs to properly process and generate Mojo artifacts within the Hatchling environment.

Yes, hatch-mojo integrates with the standard Hatchling build system to ensure that compiled .mojo sources are correctly packaged and included as Python extensions or executables in the final wheel distribution.