Skip to content

Conversation

carljm
Copy link
Member

@carljm carljm commented Aug 16, 2023

One more case of a watcher test spuriously failing because a watcher is already installed. I think this should be the last one.

@carljm carljm merged commit fce93c8 into python:main Aug 16, 2023
@miss-islington
Copy link
Contributor

Thanks @carljm for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖

@carljm carljm deleted the typewatchertest branch August 16, 2023 19:13
@bedevere-bot
Copy link

GH-108053 is a backport of this pull request to the 3.12 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.12 only security fixes label Aug 16, 2023
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Aug 16, 2023
pythonGH-107989)

(cherry picked from commit fce93c8)

Co-authored-by: Carl Meyer <carl@oddbird.net>
Yhg1s pushed a commit that referenced this pull request Aug 16, 2023
…er (GH-107989) (#108053)

gh-91051: fix type watcher test to be robust to existing watcher (GH-107989)
(cherry picked from commit fce93c8)

Co-authored-by: Carl Meyer <carl@oddbird.net>
facebook-github-bot pushed a commit to facebookincubator/cinder that referenced this pull request Aug 17, 2023
Summary:
Use type watchers instead of direct calls for handling type modifications in JIT and shadowcode.

Also backport python/cpython#107989 so the type watchers tests are resilient to there already being a type watcher installed.

Reviewed By: alexmalyshev

Differential Revision: D48340200

fbshipit-source-id: 25798b824bc231bd68f8ec7c4c81bb2fa84e3914
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news tests Tests in the Lib/test dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants