healpy version detected as 0.0.0 by pip

[ntessore]

Solution to issue cannot be found in the documentation.

• [X] I checked the documentation.

Issue

Installing healpy with conda results in a package that pip detects as version 0.0.0 and usually overwrites with its own version.

% pip list  
Package                   Version
------------------------- -------------------
...
healpy                    0.0.0
...

Installed packages

% conda list
# packages in environment at ...:
#
# Name                    Version                   Build  Channel
...
healpy                    1.16.6          py312h243f5a9_3    conda-forge
...

Environment info

shell level : 1
          conda version : 23.3.1
    conda-build version : not installed
         python version : 3.10.11.final.0
       virtual packages : __archspec=1=x86_64
                          __osx=12.7.1=0
                          __unix=0=0
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/osx-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/osx-64
                          https://repo.anaconda.com/pkgs/r/noarch
               platform : osx-64
             user-agent : conda/23.3.1 requests/2.29.0 CPython/3.10.11 Darwin/21.6.0 OSX/12.7.1
                UID:GID : 501:20
             netrc file : None
           offline mode : False

[ntessore]

This does not appear to happen with healpy==1.15.*:

% pip list | grep healpy
healpy                    1.15.2
% conda list | grep healpy
healpy                    1.15.2          py310h51a98f7_1    conda-forge

But that also leads to a py310 environment, so the difference might be on the pip side of things.

[dhomeier]

I could disect that a bit further down, 1.16.2 (available for py311) still being versioned correctly, but 1.16.5 not (1.16.3-4 are not available with miniconda). Could the setup.py install --single-version-externally-managed have become broken with newer setuptools?