Maturin doesn't work with RustPython because it's treated as an unknown interpreter.

Maturin doesn't work with RustPython because it's treated as an unknown interpreter.

Because Maturin serves as a bridge between Python and Rust, it ends up being more essential than it seems.

This issue is more of a discussion than a bug or feature request, as it takes advantage of the fact that issues receive more attention than discussions.

But there's two ways to make this work.

1. Request RustPython support from PyO3 (the creators of Maturin).
2. Create a fork of Maturin specifically for RustPython.

Pros and cons of each:

First method

Pros:

• Better integration with the Maturin environment and the PyO3 ecosystem.
• No need to patch Maturin to work with RustPython.

Cons:

• This would be unlikely to be approved due to the complexity of maintenance.

Second method

Pros:

• Integration without relying on the PyO3 committee.
• Exclusive improvements for better performance in RustPython.

Cons:

• Makes the project harder to maintain.
• Implementation may be difficult, especially for a small team.

The issue names Maturin, PyO3, and RustPython but no files, tests, or entry points. First determine how Maturin identifies interpreters and whether RustPython support belongs in PyO3 or a separate integration; the issue is done only once a concrete implementation path and acceptance criteria are agreed.