No, see this: https://deploy-preview- | Dagger | Page 1

ivory wedge Feb 22, 2024, 4:43 PM

#

Nice. I missed these docs, are they not publically released yet?

#

(trying to be a little hipster for this spike and using rye on it)

quaint shard Feb 22, 2024, 4:44 PM

#

Thats a part of https://github.com/dagger/dagger/pull/6681 🙂

GitHub

docs: Restructures developer section by vikram-dagger · Pull Reques...

#

Yeah, should work with rye. Haven't tried it yet.

ivory wedge Feb 22, 2024, 4:44 PM

#

supposedly they support pip so I am guessing yes as well

quaint shard Feb 22, 2024, 4:46 PM

#

Rye doesn't need to support pip, they need PEP 517, which means a build backend in pyproject.toml. Default backend is just the build package.

#

That's if rye builds python packages like poetry. Otherwise it's just your local tool, and doesn't affect the module at runtime.

ivory wedge Feb 22, 2024, 5:14 PM

#

If i did want to use Rye, would I need to actually modify the 3.11 python runtime container that dagger is using?

Like in other SDKs, Python modules run in a container (called the runtime container) that’s bootstrapped specifically by the Python SDK, with the necessary environment to run the module’s code. It’s currently hardcoded to run in Python 3.11, but we plan on it being configurable at some point.

#

or is this simply a matter of installing rye into the container and specifying the correct build backend in pyproject.toml

quaint shard Feb 22, 2024, 5:55 PM

#

Let me brush up on rye for a moment, so I give a proper answer 🙂

ivory wedge Feb 22, 2024, 5:56 PM

#

fwiw, i think i got something working

quaint shard Feb 22, 2024, 5:57 PM

#

According to https://rye-up.com/guide/publish/, there's no build backend. They use the default buid package. So basically rye is a local dev only tool.

#

The runtime container won't run rye.

#No, see this: https://deploy-preview-