marimo-team
chore: migrate to hatch for better local development testing
This pull request primarily focuses on transitioning the project to use Hatch for Python environment and build management, replacing previous tools like setuptools. It also includes updates to the documentation and configuration files to reflect this change.
Hatch will use uv under the hood for fast downloading, while hatch manages the orchestration of creating environment and running tasks.
This makes running tests locally much more reproducible to CI. Docs will fail until this is merged and will updates docs deployment (otherwise updating now will make other branches fail).
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| marimo-docs | ❌ Failed (Inspect) | Oct 6, 2024 10:32pm | ||
| marimo-storybook | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 6, 2024 10:32pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
@anthonywu, I'm not all that familiar with it, it does seem like the best choice to run different python versions and dep matrices locally.
Do you think you could be one of the reviewers? Would appreciate your expertise if you know it well.
@akshayka, yes that is much better. i will keep the docs and testing deps out of "[dev]" though, to encourage running them in the isolated envs