installation fails on macOS 12.1

[jpyces]

python 3.10

the error -

102 warnings generated.
clang -bundle -undefined dynamic_lookup -arch arm64 -arch x86_64 -g -L/usr/local/opt/icu4c/lib set -gx CPPFLAGS -I/usr/local/opt/icu4c/include build/temp.macosx-10.9-universal2-3.10/Levenshtein/_levenshtein.o -o build/lib.macosx-10.9-universal2-3.10/Levenshtein/_levenshtein.cpython-310-darwin.so
clang: error: unknown argument: '-gx'
clang: error: no such file or directory: 'set'
clang: error: no such file or directory: 'CPPFLAGS'
error: command '/usr/bin/clang' failed with exit code 1
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> python-Levenshtein

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

[SolebaySharp]

Same issue but on Ubuntu (Bionic Beaver, Python 3.6, 3.7, and 3.9).

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [34 lines of output]

      ... # -------> Removed 

      Levenshtein/_levenshtein.c:99:10: fatal error: Python.h: No such file or directory
       #include <Python.h>
                ^~~~~~~~~~
      compilation terminated.
      error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
      [end of output]
  
  ... # -------> Removed 
  
  × Running setup.py install for python-Levenshtein did not run successfully.
  │ exit code: 1
  ╰─> [34 lines of output]

     ... # -------> Removed 

      Levenshtein/_levenshtein.c:99:10: fatal error: Python.h: No such file or directory
       #include <Python.h>
                ^~~~~~~~~~
      compilation terminated.
      error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> python-Levenshtein

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

@shadows1003929 you might want to consider changing the title to something like 'Legacy Install Failure' seeing as it is across
Linux/Unix platforms now.