This adds new test cases for bugs reported by Thomas Heller against IronPython for ctypes and winreg:
   ctypes: the variant bool type isn't supported
   winreg: errno is not correctly set when QueryValue fails

Rather than calling QueryValue and using fail(...) if it doesn't throw, assertRaises(...) would do the trick.

Also assertEqual(..., True) can be replaced by assertTrue(...) (same for False and assertFalse).

The problem with assertRaises is I need to actually check the errno on the exception and assertRaises doesn't let me do that.

Hmm... assertTrue(...) is semantically different from assertEqual(True, ...).

Dino - if you use assertRaises as a context manager the exception is kept as an attribute on the context. You can make assertions about the exception after the with block has executed.

I'll switch to the context manager form in the 3.x branch - it looks like that's not available in the 2.x branch.

Ezio: I'm going to stick w/ assertEqual here as Michael points out these are different.  In particular I want to make sure that you can assign any true value to the ctypes field but when you read it back you get True or False regardless of the value assigned.

For your purpose indeed assertTrue() is not appropriate, however assertEqual(x, True) works for several different x, including 1.0 or 1.
Also assertRaises can be used as a context manager on 2.7 too.

Ahh, so it is in 2.7, apparently I was in a 2.6 enlistment.  I've updated the 2.x patch to use the context manager as well.

I've also switched to using assertTrue(x is True) and assertTrue(x is False) so that it's not checking precisely for the bool value based upon Ezio's feedback.

Does this need committing? Dino - do you have checkin rights?

Brett Cannon was going to try and look at it and commit it.  If you think it looks good you can commit it :)

I do not yet have commit privledges simply because I need to gen my SSH key and send that off to Brett.  I'm also hoping to get a little hand holding on the 1st few check-ins.

Well, probably better for you to get the commit bit and DIY then. :-)

Now that Dino has commit privileges and I just gave him the coordinator role, he can do the commit himself. =) Went ahead and assigned this issue to him.

And Dino, it would be helpful if you changed your username on the tracker to match your username on python-dev under "Your Details".