Third-party tests failed on Sat Jul 01 2023

[github-actions]

Runs listed here: https://github.com/python/typing_extensions/actions/workflows/third_party.yml

[JelleZijlstra]

Seems like pydantic locked typing-extensions<4.7 for PyPy

🔒 Lock failed
Unable to find a resolution for typing-extensions
because of the following conflicts:
  typing-extensions @ {root:uri}/typing-extensions-latest (from project)
  typing-extensions<4.7.0,>=4.6.0; platform_python_implementation == "PyPy" 
(from pydantic-core@2.0.1)
  typing-extensions>=4.6.0; platform_python_implementation != "PyPy" (from 
pydantic-core@2.0.1)
To fix this, you could loosen the dependency version constraints in 
pyproject.toml. See 
https://pdm.fming.dev/latest/usage/dependency/#solve-the-locking-failure for 
more details.

[A5rocks]

Specifically under their pydantic-core package: here's the PR: pydantic/pydantic-core#716.

[AlexWaygood]

Not sure I understand why this is also making the pydantic CI runs using CPython fail, as well as the pydantic CI runs using PyPy

[AlexWaygood]

If we cut 4.7.1 with #262 or a different fix for #258, I can file a PR with pydantic for them to loosen their typing_extensions pin

[AlexWaygood]

This should hopefully have been fixed by pydantic/pydantic-core#728, but the pydantic jobs on the nightly workflow will continue to fail until they (1) cut a new release of pydantic-core and (2) update the pydantic-core pin in pydantic.

Pydantic-core releases seem to come every few days, though, so this hopefully shouldn't take too long.

[AlexWaygood]

The workflow now passes again on my GitHub fork following pydantic/pydantic@ab7f805; seems this is now fixed 🎉