Alex Waygood

> I merged your cherry pick Thanks! > but it looks like the tag was already made. Ah, I didn't spot that :/ there's also the unresolved issue of the...

@svalentin I think something's gone wrong with https://github.com/python/mypy/pull/15751 (which backported a stubtest fix to the `release-1.5` branch). I can see the change included in the `1.5.0` tag and the `release-1.5`...

Looks like this might be changed in CPython, so maybe we should just wait for the next 3.12 beta rather than merging this: - https://github.com/python/cpython/pull/106401

> unless perhaps we want to enable 3.12 in CI before the next beta is available. For now could we maybe just skip the test? I can't remember the pytest...

> This is still failing for me on Python 3.12.0 beta 4. I'm leaning towards merging this. We can always revert this afterwards if it's no longer needed. Makes sense!

> We could also have a mypyc extra that includes it, like we do for dmypy or reports. I'd personally prefer this, but agree that having it as an unconditional...

Very similar traceback to #15241

- @A5rocks's PR here purports to fix two open crash reports: #15272 - It's not urgent, but I'd love it if somebody could take a look at my PR here....

Also, just to note: #15161 caused a LiteralString-related regression for typeshed that still exists on the master branch. I reported the regression here immediately after the PR was merged: https://github.com/python/mypy/pull/15161#issuecomment-1531596612....

You'll probably also want to cherry-pick this, if there is a 1.4.1 release -- our test suite was very broken by the pytest release earlier today: - [ ] https://github.com/python/mypy/pull/15505