topic: use more protective code to access publishing code There are some code path where the operation is not properly initialized and lack the new attributes. While the lack of initialization, is suspicious and I've not be able to pin point case where this happens. Currently the code crash when it encounter this situation. So we make the code more resistant to this case to prevent bad user experience.

     1

#require test-repo pyflakes

     2

     3

Copied from Mercurial core (60ee2593a270)

     4

     5

  $ cd "`dirname "$TESTDIR"`"

     6

     7

run pyflakes on all tracked files ending in .py or without a file ending

     8

(skipping binary file random-seed)

     9

    10

  $ hg locate 'set:(**.py or grep("^#!.*python")) - removed()' 2>/dev/null \

    11

  > | xargs pyflakes 2>/dev/null