phonenumberslite fails to install from source: “WARNING: Generating metadata for package phonenumberslite produced metadata for project name phonenumbers. Fix your #egg=phonenumberslite fragments”

[andersk]

$ pip install --no-binary=phonenumberslite phonenumberslite
Collecting phonenumberslite
  Downloading phonenumberslite-9.0.1.tar.gz (2.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 5.1 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package phonenumberslite produced metadata for project name phonenumbers. Fix your #egg=phonenumberslite fragments.
Discarding https://files.pythonhosted.org/packages/00/29/5024fdb4b0b4e5a25cafd30aa59a8a05abbe55dc0974dcaf9bfebeebcfeb/phonenumberslite-9.0.1.tar.gz (from https://pypi.org/simple/phonenumberslite/): Requested phonenumbers from https://files.pythonhosted.org/packages/00/29/5024fdb4b0b4e5a25cafd30aa59a8a05abbe55dc0974dcaf9bfebeebcfeb/phonenumberslite-9.0.1.tar.gz has inconsistent name: expected 'phonenumberslite', but metadata has 'phonenumbers'
  Downloading phonenumberslite-9.0.0.tar.gz (2.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 8.3 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package phonenumberslite produced metadata for project name phonenumbers. Fix your #egg=phonenumberslite fragments.
Discarding https://files.pythonhosted.org/packages/fc/03/86ef50faba4fcfaa603973af1d3d163757ba35b5c1255d721c64b551cfdb/phonenumberslite-9.0.0.tar.gz (from https://pypi.org/simple/phonenumberslite/): Requested phonenumbers from https://files.pythonhosted.org/packages/fc/03/86ef50faba4fcfaa603973af1d3d163757ba35b5c1255d721c64b551cfdb/phonenumberslite-9.0.0.tar.gz has inconsistent name: expected 'phonenumberslite', but metadata has 'phonenumbers'
  Downloading phonenumberslite-8.13.55.tar.gz (2.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 15.0 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package phonenumberslite produced metadata for project name phonenumbers. Fix your #egg=phonenumberslite fragments.
Discarding https://files.pythonhosted.org/packages/9c/b9/e37adc408dd605228020a5adc7f897353a90c597239bad52ac7fdf356f4c/phonenumberslite-8.13.55.tar.gz (from https://pypi.org/simple/phonenumberslite/): Requested phonenumbers from https://files.pythonhosted.org/packages/9c/b9/e37adc408dd605228020a5adc7f897353a90c597239bad52ac7fdf356f4c/phonenumberslite-8.13.55.tar.gz has inconsistent name: expected 'phonenumberslite', but metadata has 'phonenumbers'
  Downloading phonenumberslite-8.13.54.tar.gz (2.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 8.2 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package phonenumberslite produced metadata for project name phonenumbers. Fix your #egg=phonenumberslite fragments.
Discarding https://files.pythonhosted.org/packages/a0/b2/2d8260da29c8c8d0a5e9f6297867d88436c4b47b3c86477a263e886c106f/phonenumberslite-8.13.54.tar.gz (from https://pypi.org/simple/phonenumberslite/): Requested phonenumbers from https://files.pythonhosted.org/packages/a0/b2/2d8260da29c8c8d0a5e9f6297867d88436c4b47b3c86477a263e886c106f/phonenumberslite-8.13.54.tar.gz has inconsistent name: expected 'phonenumberslite', but metadata has 'phonenumbers'
…

(This goes on downloading and discarding different versions until the user gets bored and hits Ctrl+C.)

[daviddrysdale]

Looks like pip got stricter about metadata matching at some point in the last few years. A workaround is to fall back to the legacy resolver:

$ pip install --no-binary=phonenumberslite --use-deprecated=legacy-resolver phonenumberslite

[andersk]

The legacy resolver still emits the same warning, just ignores it. The legacy resolver is unsupported and will be removed, and there’s no equivalent for uv.

$ uv run --no-binary-package=phonenumberslite --with=phonenumberslite python
   Building phonenumberslite==9.0.1
  × Failed to download and build `phonenumberslite==9.0.1`
  ╰─▶ Package metadata name `phonenumbers` does not match given name `phonenumberslite`

[AA-Turner]

@andersk the problem is that setup.py changes which package it builds based on the presence of lite in sys.argv. This is present when building the wheel initially but not when a downstream user attempts a from-sdist rebuild. Using pip install --no-binary=phonenumberslite phonenumberslite --config-settings --global-option=lite should work, though --global-option may be deprecated.

@daviddrysdale would you be receptive to a PR that seeks to adopt pyproject.toml and the new-style declarative metadata? I'd be happy to have a go.

A

[andersk]

phonenumberslite is typically not going to be the only package being installed at a time. It may be one of many requirements of some other package, or listed in a requirements.txt file, or managed with a tool like uv. And zealously passing a lite option to every package will break many of them, whether it’s formally deprecated or not.

Shouldn’t phonenumbers simply depend on phonenumberslite for everything other than the extra data files, rather than using a bespoke system to make them build variants of each other?

[AA-Turner]

True, but equally building from source is usually only done when e.g. rebuilding a package as a redistributor. It isn't a recommended installation method when wheels are provided. I agree though that the current situation isn't ideal, hence why I suggest moving to declarative metadata (which would also entail properly defining the packages for building). The idea of having phonenumbers depend on phonenumberslite is one I hadn't considered, though -- and may make things easier.

A

[daviddrysdale]

would you be receptive to a PR that seeks to adopt pyproject.toml and the new-style declarative metadata?

@AA-Turner : Yes, that would be great – thank you!

[duthils]

I made a PR to use pyproject.toml for building: #316. Any comment welcome :)