setuptools 66 breaks conda-build

[jaimergp]

Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

What happened?

Setuptools has dropped pkg_resources.parse_version legacy behaviour, so it doesn't use LegacyVersion under the hood anymore. This results in some InvalidVersion errors in the test suite: #4732

See:

• Remove support for LegacyVersion pypa/setuptools#2497
• Drop LegacySpecifier and LegacyVersion pypa/packaging#407

Conda Info

See CI https://github.com/conda/conda-build/pull/4732

Conda Config

See CI https://github.com/conda/conda-build/pull/4732

Conda list

See CI https://github.com/conda/conda-build/pull/4732

Additional Context

This affects conda-smithy rerender too: conda-forge/conda-forge-pinning-feedstock#3973

[jakirkham]

Wonder if we are able to drop pkg_resources altogether

[jaimergp]

xref #4443

[jakirkham]

Lol had forgotten that 🤦‍♂️

[ReimarBauer]

fixating setuptools helps meanwhile

setuptools ==65.5.1

conda-forge/mss-feedstock@6fab5f0

our problem in MSS will be solved after fixing our version string, which has a tailing dot at the end.

[ReimarBauer]

I have currently a follow up problem.
Usually we install our dependencies for developers by:

mamba install mss python --only-deps

The result is a broken environment. mamba is missing, conda faces inconsistancy.

We have to do now.

mamba install mss python
conda remove mss --force

Maybe this will vanish also when I fixed our version string.

[jakirkham]

We need a repodata fix in conda-forge (defaults may need a similar fix)

Please see PR ( conda-forge/boa-feedstock#61 ). In particular comment ( conda-forge/boa-feedstock#61 (comment) ). Help making this change would be welcome :)