Samuel Freilich
Samuel Freilich
The current implementation of `asserts.equals(expected, actual)` in unittest.bzl puts just `str(value)` for each of the values in the assertion failure message. It would be nice if it gave a more...
Writing assertions on the command lines of actions of the target under test is complicated for a few reasons: * Not all actions have argv, you want to pull out...
When I run the tests with the latest version of `freezegun`, I get: ``` self = frozen_time = @freeze_time('2013-04-09', as_kwarg='frozen_time') def test_method_decorator_works_on_unittest_kwarg_frozen_time(self, frozen_time): self.assertEqual(datetime.date(2013, 4, 9), datetime.date.today()) > self.assertEqual(datetime.date(2013, 4,...
If the input coordinates are NaN, the call to `tessTesselate` segfaults in `pqInit`, since the code falsely assumes a total ordering. Possibly `tessAddCountour` should check that the values are not...
# Feature or enhancement ### Proposal: Based on [PEP 564](https://peps.python.org/pep-0564/), the `time` module has `_ns()` methods that generate timestamps of nanoseconds since the epoch. I think it might make sense...
I'm trying to dig into a crash with this repro case: ``` TEST_F(Libtess2Test, CrashRepro) { AddPolyline(tess, {{{1.f, 0.854620099f}, {0.f, -1.f}, {1.f, -3.f}, {-0.5f, 0.f}, {0.301400006f, -1.f}, {-1.f, 0.784999669f}, {-1.f, 1.f},...