Inform setuptools that Extensions are included

[jakirkham]

Fixes #641

As setuptools/pip/wheel will mark our package as pure (even though we put an extension module into it), make sure it doesn't by informing setuptools that Extensions are contained within. This should ensure that are wheels include the Python minor version they were built for.

[jakirkham]

This works! 🎉

Final name from CI:

./cucim_cu11-23.12.0a21-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

[grlee77]

Thanks, John. This looks good! I guess this may be preferable to renaming after the fact as in #644.

[jakirkham]

Based on offline discussion, we decided to go with PR ( #644 ) as it is a publicly documented API that is most consistent with how the build works

Longer term we might want to use scikit-build ( #645 ), which would make this unnecessary

[jakirkham]

Turns out wheel tags adds a new Root-Is-Purelib field to *.dist-info/WHEEL without removing the old one, which leaves the metadata in an invalid state:

$ grep 'Root-Is-Purelib' cucim_cu11-23.12.0.dist-info/WHEEL
Root-Is-Purelib: true
Root-Is-Purelib: False

So reviving this alternative approach and reverting the wheel tags change

[vyasr]

To unblock the release, can we also add (or symlink) the license into python/cucim?
Running ln -s ../../LICENSE in the python/cucim directory should do it (unless we need the 3rd party license, I don't know, but symlink that one instead if needed).

[jakirkham]

Good catch. Went ahead and symlinked both and updated pyproject.toml to list both