Can we already get rid of mxdev in cookieplone projects?

Development
1

As mentioned in the pretty new section Install Plone add-ons — Plone Documentation v6 you can have a cookieplone-based project without mx.ini but managed by uv. Then you can use uv add --editable ../collective.easyform to have checkouts managed by uv.

Does that mean we can get rid of mxdev and use uv with [tool.uv.sources] for installation and management of checkouts and [tool.uv] constraint-dependencies = xxx for overrides? That would be really nice but how so? All projects created with cookieplone still have mx.ini afaik and in [tool.uv] it is always managed = false.

2

It’s a work in progress.

The monorepo project template was updated to use a uv-managed installation during the sprint in Bucharest: Project: Manage backend installation with uv by ericof · Pull Request #352 · plone/cookieplone-templates · GitHub . That’s why we then scrambled to update the docs to cover this approach, which was merged today.

mxdev may still be useful for actually doing the checkout. There’s a PR, submitted yesterday, to make it update [tool.uv.sources]: Edit pyproject.toml file's `tool.uv.sources` option if it is a uv-managed project by erral · Pull Request #81 · mxstack/mxdev · GitHub. More work would then be needed to integrate this into the project template and update the docs.

The Classic UI project template will still use mxdev until someone updates it.