Chris Rose
Chris Rose
I think you've identified a real bug; I would expect the matcher to handle mixed types with no issue.
@brunns I think the answer to your question (sorry, left it sitting) is cleared up in #215: I am okay with `assert_that(greater_than(1, "a"))` being resolved as not-matching, rather than TypeError-raising.
what you're describing makes sense to me, at least in principle. I would want to see examples in the pull request, but I can easily see merging it. if possible...
Just to clarify, this is when numpy tests are running; this doesn't happen in non-numpy testing.
@lindycoder can you check with 2.0.4 please? I _believe_ we've fixed this in the latest release, but I would like to be sure.
The CI setup has been significantly revamped since this was created (and I have not had time to think through it in the interim). Please rebase this PR and let's...
Interestingly, this only happens if I watch a _very large_ tree of files. If I watch a subset of it, the sync is fine, but if I watch the large...
I use the fish shell, where I definitely _can_ get at this information. Would a PR that enables this _where possible_ be acceptable? I know I can get it on...
Yeah, it ... helps. I guess I'd consider, if I were you, leaving this issue open to track that there is a gap, and resolving it when that documentation exists....
I have a further question: Since this kind of testing requires constructing the `app` object differently, but the object is created at the module level, does someone there have a...