0.70.17 sdist has python-tag = py313 hardcoded, rendering it incompatible with other Python versions

[mgorny]

For example, using Python 3.12:

$ pip install --no-binary=multiprocess multiprocess==0.70.17
Collecting multiprocess==0.70.17
  Using cached multiprocess-0.70.17.tar.gz (1.8 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: dill>=0.3.9 in ./venv/lib/python3.12/site-packages (from multiprocess==0.70.17) (0.3.9)
Building wheels for collected packages: multiprocess
  Building wheel for multiprocess (pyproject.toml) ... done
  Created wheel for multiprocess: filename=multiprocess-0.70.17-py313-none-any.whl size=147987 sha256=99b8a80bfdf46838b858e45193184c2054452d36ab7375f60de07ccb79e75fce
  Stored in directory: /home/mgorny/.cache/pip/wheels/dc/81/fa/c946c329f0033701d97715d4fdd2d217c495d1cbc6717c9c81
Successfully built multiprocess
Installing collected packages: multiprocess
Successfully installed multiprocess-0.70.17
$ pip check
multiprocess 0.70.17 is not supported on this platform

Note that it incorrectly produced a py313 wheel.

[mmckerns]

Ah, ok, I must have uploaded the wrong source tarball (i.e. the one built when building the 3.13 wheel). In that case, I'll release a 0.70.17.1

[mgorny]

I've played a bit and I was able to control the tags from setup.py automatically, which should avoid this kind of problem in the future. I've filed #197 for this.

[sahiljhawar]

@mmckerns I am having the same issue during conda build process. Can you please push a fix? For now I can restrict to previous version in my recipe.

[mmckerns]

@sahiljhawar: I will get to a new release for multiprocess with this corrected as soon as I can. I'm on some travel and haven't had an opportunity post-release. It might take another week to get to it, but it's at the top of my to do list