Repository navigation
Run mypy job with Python 3.11 once it is supported #240
Description
Description
We should revert c3bfe66 once mypy is sorted out (and if it's not mypy fault, then whatever we are doing wrong).
Maybe related to python/mypy#12840, maybe we need to open a new issue over there?
Reacted by Ben Mares
Activity
[-]Run mypy job in Python 3.11 once it is supported[/-][+]Run mypy job with Python 3.11 once it is supported[/+]ricardoV94 commentedon Mar 11, 2023
I didn't save the run, but this was the error:
Even though it's there in main
https://github.com/pypa/setuptools/blob/245d72a8aa4d47e1811425213aba2a06a0bb64fa/setuptools/_distutils/errors.py#L112-L113
ricardoV94 commentedon Apr 17, 2023
It also cropped up on a Python 3.10 job now, so it must be something else: https://github.com/pymc-devs/pytensor/actions/runs/4712555504/jobs/8357675677?pr=276
@michaelosthege do you have any ideas?
maresb commentedon Apr 17, 2023
Looks like a problem with
setuptools-typeswhich would be fixed by python/typeshed#10057 and #277ricardoV94 commentedon Apr 17, 2023
Awesome 😎
maresb commentedon Apr 17, 2023
My typeshed PR has already been merged. A quick glance at their GH Actions suggests that there will soon be an automatic release to https://pypi.org/project/types-setuptools/#history. Once that's out, #277 should pass.