Monkeypatch the CFFI Verifier to prevent the implicit compile

![ma9vmor](https://cloud.githubusercontent.com/assets/145979/5050783/00fb220e-6bff-11e4-88f7-1d423dd9388e.gif)

I can switch to that. I don't have a reason other than it is what popped into my head first and I didn't bother to think any more on it. 


> On Nov 14, 2014, at 3:54 PM, Alex Gaynor <notifications@github.com> wrote:
> 
> In tests/hazmat/bindings/test_utils.py:
> 
> > @@ -23,3 +28,12 @@ def test_create_modulename():
> >      assert name == "_Cryptography_cffi_bcba7f4bx4a14b588"
> >      name = utils._create_modulename(cdef_source, source, "3.2")
> >      assert name == "_Cryptography_cffi_a7462526x4a14b588"
> > +
> > +
> > +def test_implicit_compile_explodes():
> > +    # This uses a random comment to make sure each test get's it's own hash
> > +    random_comment = hashlib.md5(os.urandom(24)).hexdigest()
> Why are we md5'ing os.urandom()? Can't we just binascii.hexlify(os.urandom(n))?
> 
> —
> Reply to this email directly or view it on GitHub.
>