John Snow <js...@redhat.com> writes: > In a forthcoming series that adds a new QMP documentation generator, it > will be helpful to have a linting baseline. However, there's no need to > shuffle around the deck chairs too much, because most of this code will > be removed once that new qapidoc generator (the "transmogrifier") is in > place. > > To ease my pain: just turn off the black auto-formatter for most, but > not all, of qapidoc.py. This will help ensure that *new* code follows a > coding standard without bothering too much with cleaning up the existing > code. > > Code that I intend to keep is still subject to the delinting beam. > > Signed-off-by: John Snow <js...@redhat.com> > Reviewed-by: Markus Armbruster <arm...@redhat.com>
Not an objection, just so you know: I still see a few C0411 like 'third party import "import sphinx" should be placed before ...' R-by stands.