Move mypy and versioneer settings to pyproject.toml

[Armavica]

Description

Related Issue

• Closes #
• Related to #

Checklist

• Checked that the pre-commit linting/style checks pass
• Included tests that prove the fix is effective or that the new feature works
• Added necessary documentation (docstrings and/or example notebooks)
• If you are a pro: each commit corresponds to a relevant logical change

Type of change

• New feature / enhancement
• Bug fix
• Documentation
• Maintenance
• Other (please specify):

---

📚 Documentation preview 📚: https://pymc--7382.org.readthedocs.build/en/7382/

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.18%. Comparing base (1b67888) to head (0e984d0).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7382   +/-   ##
=======================================
  Coverage   92.18%   92.18%           
=======================================
  Files         103      103           
  Lines       17258    17258           
=======================================
  Hits        15909    15909           
  Misses       1349     1349           

[maresb]

I took a very quick look. Very exciting, but there's a problem:

$ python -m build .
...
Successfully built pymc-0.0.0.tar.gz and pymc-0.0.0-py3-none-any.whl

It's picking up the version as 0.0.0. In contrast, on main:

Successfully built pymc-5.15.1+52.gc2c46a764.tar.gz and pymc-5.15.1+52.gc2c46a764-py3-none-any.whl

[Armavica]

@maresb You are right, it looks like versioneer is not ready yet to deal with builds configured from pyproject.toml. I moved the settings of mypy and versioneer to pyproject.toml but kept the build in setup.py, I think this is the most that we can do for now. I think it builds fine now.

[maresb]

I carefully compared the build artifacts before and after, and this looks good to go!

[maresb]

It's great to get rid of versioneer.py, thanks @Armavica!!!