Rewrite assert statements, refs #12

[sobolevn]

This is still a WIP.

I have several questions:

1. How does get_arg_offset suppose to work? I am bit a lost with this approach 🙂
2. Do we need to handle msg part of assert expr, msg? Because not all self.assert*() methods support it

Closes #12

[isidentical]

How does get_arg_offset suppose to work? I am bit a lost with this approach

Yeah, it is not a very straight forward solution. But basically it is for adjusting comments appropriately when the initial version of the same call (e.g assertTrue(a < 10, msg="x") has 2 arguments) has more/less arguments than the refactored version (e.g assertLessEquali(a, 10, msg="x") has 3 arguments).

I don't think it is something that this refactor should worry about. Perhaps try returning 0?

Do we need to handle msg part of assert expr, msg? Because not all self.assert*() methods support it

I guess it serves the same purpose, so we can use it. I don't think we need to add it in this PR.

[isidentical]

I didn't look in detail yet, but this is impressive work (I thought the existing refactoring infrastructure wouldn't work with asserts, but from what I understand by looking at the tests it seem to work pretty well.)

One Q: There is a special mode in teyit called --show-stats, which dumps the refactor results after each run. I wonder whether we can integrate this to there, so we can see how many asserts get refactored. It is a pretty useful metric, and if you see the Teyit step in CPython run it helps us to ensure we don't make any problematic change.