Loading
Test assertion failure due to class name
BridgeDB attempted to use metaprogramming to define the class name for
bridgedb/filters.py's byIPv4 and byIPv6. Rather than puzzling that out simply
changing the assertion. Honestly it would be nice if BridgeDB did less of this
- it makes the code a lot harder to follow.
This sidesteps...
Traceback (most recent call last):
File "/home/atagar/Desktop/tor/bridgedb/bridgedb/test/test_email_distributor.py", line 237, in test_EmailDistributor_prepopulateRings
self.failUnlessIn("IPv4", "".join([str(ringname) for ringname in ringnames]))
File "/usr/local/lib/python3.5/dist-packages/twisted/trial/_synctest.py", line 492, in assertIn
% (containee, container))
twisted.trial.unittest.FailTest: 'IPv4' not in 'frozenset({<function byIPv.<locals>._byIPv at 0x7f954be99d08>})frozenset({<function byIPv.<locals>._byIPv at 0x7f954be99d90>})'
Test results changed as follows...
before: FAILED (skips=115, failures=18, successes=851)
after: FAILED (skips=115, failures=17, successes=852)