feat: adopt maturin

[kemingy]

• close feat: try to build with ABI3 #604 , this is using bin instead of pyo3 binding, so it has nothing to do with the ABI3

benefits

• better build & release toolchain, both for devs & users
• packaging has nothing to do with the Python version
• more platform support

defects

• we already use the name mosec for both rust/py packages, this will add a mosec bin to the scripts, so people may accidentally execute mosec xxx and get an error (since it's not meant to be called directly by the users)
• no more scm version from git, we will use the one in Cargo.toml

Copilot reviewed 5 out of 8 changed files in this pull request and generated no comments.

Files not reviewed (3)

• MANIFEST.in: Language not supported
• Makefile: Language not supported
• requirements/dev.txt: Language not supported

Comments suppressed due to low confidence (1)

mosec/runtime.py:273

• Ensure that the 'mosec' binary is correctly located in the PATH to avoid runtime errors. Previously, the path was explicitly set using importlib_files.

self.process = subprocess.Popen([str("mosec"), config_path])

[kemingy]

I have verified that this works for:

• miniconda
• uv
• Ubuntu system python & pip (with --break-system-packages, yes it's not recommended but who knows)
• python official docker image
• envd
  • default env cannot install mosec since it's still using a legacy Ubuntu20.04, tracked feat: upgrade to ubuntu 22.04 tensorchord/envd#1939
  • envd v1 with dev(image="ubuntu:22.04") works

[kemingy]

There are many ways to install Python packages, but if they're managed by modern tools, I think they should work.

One common issue from envd is that the user installs with system-level pip but doesn't have the write permission, so the bin is placed to their /home/$USER/.local/bin, this may not be in their PATH. I don't remember how to reproduce now.

Copilot reviewed 6 out of 14 changed files in this pull request and generated no comments.

Files not reviewed (8)

• MANIFEST.in: Language not supported
• Makefile: Language not supported
• requirements/dev.txt: Language not supported
• setup.py: Evaluated as low risk
• tests/test_service.py: Evaluated as low risk
• mosec/init.py: Evaluated as low risk
• Cargo.toml: Evaluated as low risk
• .github/workflows/nightly.yml: Evaluated as low risk

Comments suppressed due to low confidence (1)

mosec/runtime.py:273

• Using a hardcoded string for the executable path might cause issues if the executable is not in the system's PATH. Consider using a resolved path instead.

self.process = subprocess.Popen([str("mosec"), config_path])

[lkevinzc]

Ubuntu system python & pip (with --break-system-packages, yes it's not recommended but who knows)

I have a minor concern with this. Here the python / pip refers to /usr/bin/python?

[kemingy]

I have a minor concern with this. Here the python / pip refers to /usr/bin/python?

Not exactly. It's installed by apt install python3 python3-pip. So it's /usr/bin/python3. It's still recognized as system python. The system will warn that users need to create venv to install packages.

[lkevinzc]

Not exactly. It's installed by apt install python3 python3-pip. So it's /usr/bin/python3. It's still recognized as system python. The system will warn that users need to create venv to install packages.

I see, thanks for clarification. Since almost all commonly used installation methods work well, let's merge this nice update to make the build simpler!