David R. MacIver

> I am not sure it should be attempting to unwrap the modulo. Really? Why not? This might just be my misunderstanding matters, but I'd expect that if you had...

> All I can is that ternary operators are a mess. Yeah, operator resolution is already my least favourite part of Python even before you get into C extensions and...

Might be a Python version thing? This was on 3.6.0. Sorry, I should have said that up front.

So I've tried the following in a virtualenv for each of Python 2.7.13, 3.6.0 and 3.6.1 and I get a segfault in all three: ``` pip uninstall wrapt -y WRAPT_INSTALL_EXTENSIONS=true...

Yeah, absolutely. I'm keen for this to exist, but am a bit short on spoons at the moment so haven't been prioritising shrinking challenge work.

Ideally it would be possible to make this work by just reusing the code from the existing Hypothesis shrinking challenges, but I'm not sure if that's easier than maintaining a...

> So other command line arguments that match the pattern something=something should call setenv before the run loop? Yup, exactly.

Forgot to say at the time: Thanks for bringing this up. As per discussion elsewhere, it'll be a little while before I get to this, but I'm definitely going to...

Nope. This is specifically about running each example in its own subprocess, not whole tests.

Filtering the bounds is also a perfectly reasonable thing to do I think - filter is only really problematic if the event is common, and hitting exact bounds shouldn't be.