Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daily tests failed on Fri Feb 09 2024 #11383

Closed
github-actions bot opened this issue Feb 9, 2024 · 1 comment · Fixed by #11384
Closed

Daily tests failed on Fri Feb 09 2024 #11383

github-actions bot opened this issue Feb 9, 2024 · 1 comment · Fixed by #11384
Labels
help wanted An actionable problem of low to medium complexity where a PR would be very welcome

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2024

Runs listed here: https://github.com/python/typeshed/actions/workflows/daily.yml

@github-actions github-actions bot added the help wanted An actionable problem of low to medium complexity where a PR would be very welcome label Feb 9, 2024
@AlexWaygood
Copy link
Member

AlexWaygood commented Feb 9, 2024

Stdlib stubtest errors due to the new patch releases of 3.11 and 3.12.

The __non_callable_proto_members__ ones on 3.12 just need to be allowlisted for now (should probably ignore them more systematically in stubtest). The asyncio one looks like it might be a true positive, though

JelleZijlstra pushed a commit to python/mypy that referenced this issue Feb 9, 2024
This is added to all protocol classes on Python 3.12.2+ (it was added in
a patch release of 3.12 as part of a bugfix). There's no reason why
you'd want to explicitly include it in a stub (and doing so would lead
the type checker to incorrectly conclude that you wanted a member
literally called `__non_callable_proto_members__`)

Cf. python/typeshed#11384 and
python/typeshed#11383
cdce8p pushed a commit to cdce8p/mypy that referenced this issue Feb 10, 2024
This is added to all protocol classes on Python 3.12.2+ (it was added in
a patch release of 3.12 as part of a bugfix). There's no reason why
you'd want to explicitly include it in a stub (and doing so would lead
the type checker to incorrectly conclude that you wanted a member
literally called `__non_callable_proto_members__`)

Cf. python/typeshed#11384 and
python/typeshed#11383

(cherry picked from commit 517f5ae)
cdce8p pushed a commit to cdce8p/mypy that referenced this issue Feb 10, 2024
This is added to all protocol classes on Python 3.12.2+ (it was added in
a patch release of 3.12 as part of a bugfix). There's no reason why
you'd want to explicitly include it in a stub (and doing so would lead
the type checker to incorrectly conclude that you wanted a member
literally called `__non_callable_proto_members__`)

Cf. python/typeshed#11384 and
python/typeshed#11383

(cherry picked from commit 517f5ae)
JelleZijlstra pushed a commit to python/mypy that referenced this issue Feb 10, 2024
This is added to all protocol classes on Python 3.12.2+ (it was added in
a patch release of 3.12 as part of a bugfix). There's no reason why
you'd want to explicitly include it in a stub (and doing so would lead
the type checker to incorrectly conclude that you wanted a member
literally called `__non_callable_proto_members__`)

Cf. python/typeshed#11384 and
python/typeshed#11383

(cherry picked from commit 517f5ae)

Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted An actionable problem of low to medium complexity where a PR would be very welcome
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant