-
Notifications
You must be signed in to change notification settings - Fork 587
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
Add and use realize
and avoid_realization
backend hooks
#4029
Conversation
aside from minor tactical comments above, this looks good to me! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Should we synchronise our release with hypothesis-crosshair, and update he version that our extra depends on?
good point, let's wait to sync 👍. Wouldn't be a great first experience if |
Yup yup. These are the correct changes, right? Shipped in 0.0.7 |
Let's cherrypick #4032 (+ a |
That plan sounds perfect to me, one moment... ah, merge conflicts. Simpler to just run |
post_test_case_hook
has been renamed torealize
and is used in more places where we want to realize symbolic valuesavoid_realization
backend class variable added, which backends can set to disable features that would cause premature realizationhypothesis.provisional.realize
as part of our unstable-but-public api, to address Storing symbolic values outside of the test case lifetime pschanely/hypothesis-crosshair#7 among others. If we want to make this less public, we can put it inhypothesis.internal.conjecture.data
for now.@pschanely here are the local modifications I made to hypothesis-crosshair:
This includes a fix for observability crashes (#3914 (comment)). However, I get the following z3 unknown sat error when running crosshair with observability - any ideas @pschanely?