> Right. My point was that since we dont care if they are there or not > the test should not test that they are there and fail if they are not. > So if there is an easy way to ignore them in this new test_pypy_c > framework (which is very cool by the way), we should. If it's not easy > I'm fine with keeping the test as it is. My main motivation here is to > learn about the new framework :)
ah, I understand now. No, ignoring all force_tokens at once is not possible at the moment, but I agree that it would be a nice feature, I think I'll implement it later. Btw, I fear I need more of your help with test_silly_max and test_iter_max (see 2e5bd737be0c): what do we want to check there? _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
