Skip to content

Add Python 3.13 to list of allowed Python versions#11411

Merged
charliermarsh merged 1 commit intomainfrom
charlie/py313
May 13, 2024
Merged

Add Python 3.13 to list of allowed Python versions#11411
charliermarsh merged 1 commit intomainfrom
charlie/py313

Conversation

@charliermarsh
Copy link
Copy Markdown
Member

Summary

I believe we're already "Python 3.13-ready"? The main Ruff-impacting change I see in https://docs.python.org/3.13/whatsnew/3.13.html is PEP 696 which Jelle added in #11120.

Base automatically changed from charlie/std to main May 13, 2024 16:27
@charliermarsh charliermarsh enabled auto-merge (squash) May 13, 2024 16:29
@charliermarsh charliermarsh merged commit 6ed2482 into main May 13, 2024
@charliermarsh charliermarsh deleted the charlie/py313 branch May 13, 2024 16:35
@github-actions
Copy link
Copy Markdown
Contributor

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

@AlexWaygood
Copy link
Copy Markdown
Member

I guess one other thing we could do is update UP035 to emit a diagnostic if --target-version=py313 has been selected and a user imports typing.TypeIs, warnings.deprecated, typing.ReadOnly, typing.NoDefault typing.get_protocol_members or typing.is_protocol from typing_extensions rather than typing

@charliermarsh
Copy link
Copy Markdown
Member Author

Makes sense, mind filing an issue (or PRing it)? :)

@AlexWaygood
Copy link
Copy Markdown
Member

Makes sense, mind filing an issue (or PRing it)? :)

#11413

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants