If no one has started or done this, I would like to work on a product for this issue resolution.

Hi! I'm currently working on the windows version of this. If you would like, the MacOS could benefit from this as well.

Thank you for getting back to me so quickly. This issue is all yours. I am working under windows as well.

Thank you! I just gave it a very light skim but being accessible to non-command-line users should help our reach tremendously.

I can't find where I suggested it, but I think "editable" (running from python source .py files) should be our default/preferred/only way of running beets in the documentation.

https://beets.readthedocs.io/en/stable/faq.html#run-the-latest-source-version-of-beets

It encourages new users to become new developers of light features/bug fixes, and encourages understanding how beets works.

I am not sure that “editable” Python installation should be presented in the documentation as the default/preferred way of running Beets. But I am definitely sure that it shouldn’t be presented as the only way.

For folks who want to contribute to Beets, I think it's great to encourage them to run the latest version in editable mode. Many people do not fall in that category, and those users are arguably better served by packaged, stable releases.

Plus, that section of the documentation needs work before it could even be used to encourage folks to run in editable mode. For starters, setup.py does not exist any longer, so the suggested python setup.py install option will fail.

Perhaps most importantly, it is not clear from those docs how to install Beets in editable mode and install optional packages. For example, how would someone install Beets in editable mode with the following optional packages? This section of the documentation does not cover this at all.

python -m pip install beets[chroma,discogs,fetchart,lastgenre,lyrics,mpdstats,plexupdate,web]

Editable mode is awesome, and I use it all the time for projects that I maintain. But it is often not the best installation option for end users, and frequently becomes a crutch for projects that often go way, way too long between packaged releases. (Ahem.)

Hi!

Has there been any progress on this one?

@antebudimir: Please allow me to refer you to Any Updates?

Yeah, that does and doesn't make sense because it happened not once that I stumbled upon a repo that didn't follow this logic and there actually was something happening in the meantime that wasn't put to paper. 😉

Thanks either way.