#867 run pylint check during build to catch new errors
Closed: Fixed None Opened 13 years ago by jhrozek.

We should run pylint during every build to catch new errors. This is not easy with stock pylint as we use many of the dynamic features of python (which is a good thing) and pylint has hard time coping with them.

I started working on new plugin that allow smarted blacklisting and discovery of attributes, but haven't had time to make it 100% for the January deadline, hence this ticket.


Honza will take a look. I transfered my WIP patch to him.

Metadata Update from @jhrozek:
- Issue assigned to jcholast
- Issue set to the milestone: FreeIPA 2.1 - 2011/08 (Final)

7 years ago

Login to comment on this ticket.

Metadata