Skip to main content

Mojo

Mojo is a systems programming language specifically designed for high-performance AI infrastructure and heterogeneous hardware. Our vision for Mojo is to be the one programming language developers need to target diverse hardware—CPUs, GPUs, and other accelerators—using Python's intuitive syntax combined with modern systems programming capabilities. Of course, Mojo also provides strong interoperability with Python.

NOTE: Not available for Windows.

What's in mojo-compiler

The mojo-compiler package includes the minimal dependencies required to build and run Mojo code, such as the Mojo compiler and standard library. It's smaller than the full mojo package and it's useful for environments where you only need to execute Mojo code. For example, mojo-compiler is good if you want it just to run Mojo in a production environment or when you're programming in Python and calling into a Mojo package (but not writing new Mojo code).

The mojo-compiler doesn't include the Mojo language server (LSP), LLDB debugger tools, Mojo code formatter, or Mojo REPL. For a complete developer installation, we recommend the mojo package instead.

Get started with pip

  1. Install Mojo:

    pip install mojo-compiler
    

    If you want the nightly build, instead use:

    pip install --pre mojo-compiler \
      --extra-index-url https://whl.modular.com/nightly/simple/
    
  2. Write some code:

    # hello.mojo
    def main():
        print("Hello, World!")
    
  3. Run the code:

    mojo hello.mojo
    
    Hello, World!
    

Using pip is great for existing Python-based environments, but if you're getting started for the first time, we recommend instead installing with pixi or uv. For more information, see the Mojo quickstart guide.

Metadata

Release files for mojo-compiler 1.2.0

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

Built distributions (wheels)

Table of built distributions (wheels) for mojo-compiler 1.2.0
File Interpreter ABI Platform Actions
mojo_compiler-1.2.0-py3-none-manylinux_2_34_x86_64.whl Python 3 none Linux glibc 2.34+ x86-64 Details for mojo_compiler-1.2.0-py3-none-manylinux_2_34_x86_64.whl
mojo_compiler-1.2.0-py3-none-manylinux_2_34_aarch64.whl Python 3 none Linux glibc 2.34+ ARM64 Details for mojo_compiler-1.2.0-py3-none-manylinux_2_34_aarch64.whl
mojo_compiler-1.2.0-py3-none-macosx_13_0_arm64.whl Python 3 none macOS 13.0+ ARM64 Details for mojo_compiler-1.2.0-py3-none-macosx_13_0_arm64.whl

Total release size: 233.1 MB

Release files / mojo_compiler-1.2.0-py3-none-manylinux_2_34_x86_64.whl

Download URL mojo_compiler-1.2.0-py3-none-manylinux_2_34_x86_64.whl
Size 81.8 MB
Tags Linux glibc 2.34+ x86-64 Python 3
SHA-256 checksum
How to use checksums
3ee34a3b26c6cccaa9523a0e8db8f67bea954497d782d97c9e61c3c4ecbdac7b
BLAKE2b-256 checksum
How to use checksums
548b2758e8a2207793613d386f41e36f2bfd28837b157a659518c7b7474f7eb3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.3

Release files / mojo_compiler-1.2.0-py3-none-manylinux_2_34_aarch64.whl

Download URL mojo_compiler-1.2.0-py3-none-manylinux_2_34_aarch64.whl
Size 78.6 MB
Tags Linux glibc 2.34+ ARM64 Python 3
SHA-256 checksum
How to use checksums
72d6f8321a50136945598ab4b9874e9980bd03103bf93545444b4448919e48c9
BLAKE2b-256 checksum
How to use checksums
62c6c716f593f140abf9cf40dd44a1b6a4745ead22cd3fd03cc856b024e6c799
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.3

Release files / mojo_compiler-1.2.0-py3-none-macosx_13_0_arm64.whl

Download URL mojo_compiler-1.2.0-py3-none-macosx_13_0_arm64.whl
Size 72.7 MB
Tags Python 3 macOS 13.0+ ARM64
SHA-256 checksum
How to use checksums
bc1777d9b3cf4522ee213cc83876b1955499aec2aa8dd8a75ce477f0cd227a90
BLAKE2b-256 checksum
How to use checksums
d60cdf22d1807e2bddebd992caee411e6cbe0c5d41834e36bff883f4a7d95fc3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.3

Security for mojo-compiler 1.2.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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