view setup.cfg @ 6298:b4f9b7e468ee stable

topic: invalidate the topic cache when branchcache is invalidated

The branchmap is cleared in the superclass function, but I didn't see any sign
that this is ever cleared.

This fixes an issue in TortoiseHg where stale topic labels appear in certain
cases, such as if a commit has a topic and is stripped, and an unrelated commit
is pulled in from a remote repo.  Additionally, it fixes an issue with the topic
display in TortoiseHg and cmdserver when using `hg rollback`.  In the new test,
the result of the command that applies `topic2` without this fix was:

    6 d (topic2)
    5 c (topic2)
    4 b (topic1)
    0 a ()

The tie in was that rev 4 used to be `topic1` before the rollback.  Also note
that without the fix, the final log command printed the following, even though
it showed no signs of `topic1`, and nothing should have changed:

    active topic 'topic1' grew its first changeset
    (see 'hg help topics' for more information)

[flake8]
ignore =
         #closing bracket does not match indentation of opening bracket's line
         E123,
         # closing bracket does not match visual indentation
         E124,
         # visually indented line with same indent as next logical line
         E129,
         # at least two spaces before inline comment
         E261,
         # too many leading '#' for block comment
         E266,
         # expected 2 blank lines, found 0
         E302,
         # expected 2 blank lines after end of function or class
         E305,
         # module level import not at top of file
         E402,
         # line too long (82 > 79 characters)
         E501,
         # do not assign a lambda expression, use a def
         E731,
         # class names should use CapWords convention
         N801,
         # line break occurred before a binary operator
         W503
builtins=xrange, execfile