beetbox
Update poetry command
I was getting my development environment set up so I could start contributing code again (yay!) when I noticed that the docs are out of date. poetry shell is no longer part of the core poetry tool, but a plugin. Using poetry env activate is given as a replacement. This just updates the docs to reflect that. I also added a shortcut so people could understand how to install all the extras, since that's pretty necessary for developers.
- [ ] Documentation. (If you've added a new command-line flag, for example, find the appropriate page under
docs/to describe it.) - [ ] Changelog. (Add an entry to
docs/changelog.rstto the bottom of one of the lists near the top of the document.) - [ ] Tests. (Very much encouraged but not strictly required.)
I think before we'd change this, we would want to look into bumping our poetry version above v2. We're still specifying poetry <2.0 which means that the poetry shell command would still be the recommended way to set up the environment.
I think before we'd change this, we would want to look into bumping our poetry version above v2. We're still specifying poetry <2.0 which means that the
poetry shellcommand would still be the recommended way to set up the environment.
Indeed, @Serene-Arc see https://github.com/beetbox/beets/issues/5783 for the context.
@snejus @wisp3rwind perhaps it's time to try a switch to uv, or perhaps implementing a fix to the issue in #5783 at least? Is there any particular reason it's not moved forwards at all? I would prefer using it over poetry and pipenv and I'm willing to investigate the integration (and this isn't a real reason, but I do so enjoy supporting rust tools).
@snejus @wisp3rwind perhaps it's time to try a switch to
uv, or perhaps implementing a fix to the issue in #5783 at least? Is there any particular reason it's not moved forwards at all? I would prefer using it over poetry and pipenv and I'm willing to investigate the integration (and this isn't a real reason, but I do so enjoy supporting rust tools).
Tbh, I’d also prefer using uv, but there are a few arguments against adopting it right now, mainly that it would further segregate our development env across the various subpackages. Still, if you want to evaluating a uv-based setup for beets, you can take a look at https://github.com/beetbox/mediafile/pull/87, which replaces poetry & pipx with uv in the mediafile package. It may serve as a useful reference point.
The reason why we pinned poetry is here: https://github.com/beetbox/beets/issues/5770