No package metadata was found for beets

[j-peeters]

Hi all,

I did something stupid I guess, brew doctor told me that I had unlinked kegs in my Cellar among which [email protected]. I thought that can't be right so I followed the suggestion to do brew link [email protected]. It asked me to overwrite existing links and I did that.
But well after that Beets didn't work anymore and it throws the following error:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.10/bin/beet", line 33, in <module>
    sys.exit(load_entry_point('beets==1.6.1', 'console_scripts', 'beet')())
  File "/Library/Frameworks/Python.framework/Versions/3.10/bin/beet", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/local/Cellar/[email protected]/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/metadata/__init__.py", line 957, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/local/Cellar/[email protected]/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/metadata/__init__.py", line 548, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for beets

brew doctor also mentioned:

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
  /Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10-config
  /Library/Frameworks/Python.framework/Versions/3.10/bin/python3-config

This might also be something I did wrong at some point and needs fixing.

When trying to understand the problem I found the Command not found FAQ on Read the Docs.

So my guess is that I either need to fix something with my Python and/or add something to my PATH. But I got stuck there.

I'm running the source version of Beets that I pulled from Github. It was a bit on the edge of my knowledge doing that but I went to the source version when there where some incompatibility issues with plugins in Beets 1.5. Maybe not needed anymore to run from source. So I considered uninstalling to fix this.

Beets is currently installed here:

$ pip show -f beets
Name: beets
Version: 1.6.1
Location: /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/beets-1.6.1-py3.10.egg
Requires: confuse, jellyfish, mediafile, munkres, musicbrainzngs, pyyaml, unidecode
Required-by: beets-bpmanalyser, beets-describe
Files:
Cannot locate RECORD or installed-files.txt

I read the post at Superuser but I noticed that I was unsure about the current location of where Beets is in stalled and what then to add to PATH.

Sorry for the long post but hopefully any of you know how I can best approach these problems and how to repair Beets. It has become a indispensable tool for managing my music library. So thanks for all the work on it!

Thanks, Jan

[j-peeters]

A simple pip uninstall beets and 'pip install beets` solved my problem. Now on a working 1.6 (instead of source 1.6.1).
I leave the long post before here for reference.