New option for the multi-statement warning to allow single-line if statements.

Allow to run pylint as a python module 'python -m pylint' (anatoly techtonik).

Various fixes to epylint

Bug fixes:

Avoid false used-before-assignment for except handler defined identifier used
on the same line (#111).

'useless-else-on-loop' not emited if there is a break in the else clause of
inner loop (#117).

Drop 'badly-implemented-container' which caused several problems in its
current implementation.

Don't mark input as a bad function when using python3 (#110).

Use attribute regexp for properties in python3, as in python2

Fix false-positive 'trailing-whitespace' on Windows (#55)

Other:

Replaced regexp based format checker by a more powerful (and nit-picky)
parser, combining 'no-space-after-operator', 'no-space-after-comma' and
'no-space-before-operator' into a new warning 'bad-whitespace'.

Create the PYLINTHOME directory when needed, it might fail and lead to
spurious warnings on import of pylint.config.

Fix setup.py so that pylint properly install on Windows when using python3.

Various documentation fixes and enhancements

Packages will be available in Logilab's Debian and Ubuntu repository in the next few weeks.

Please forward it to whom may be interested, underlining that pizzas
will be offered to refuel the chatters ;)

Conveniently placed a week after the Salt Conference, topics will
include anything related to salt and its uses, demos, new ideas,
exchange of salt formulas, commenting the talks/videos of the
saltconf, etc.

If you are interested in Salt, Python and Devops and will be in Paris at that time, we
hope to see you there !

Since then, I somewhat continued to use the continuous integration (CI) service we provide on logilab.org to run tests on new commits, and to do the release job (publish a tarball on pypi, on our web site, build Debian and Ubuntu packages, etc.). This is fine, but not really handy since the logilab.org's CI service is not designed to be used for projects hosted elsewhere. Also I wanted to see what others have to offer, so I decided to find a public CI service to host Pylint and Astroid automatic tests at least.

Here are the results of my first swing at it. If you have others suggestions, some configuration proposal or whatever, please comment.

The first one I actually tested, also the first one to show up when looking for "bitbucket continuous integration" on Google is https://drone.io. The UI is really simple, I was able to set up tests for Pylint in a matter of minutes: https://drone.io/bitbucket.org/logilab/pylint. Tests are automatically launched when a new commit is pushed to Pylint's Bitbucket repository and that setup was done automatically.

Trying to push Drone.io further, one missing feature is the ability to have different settings for my project, e.g. to launch tests on all the python flavor officially supported by Pylint (2.5, 2.6, 2.7, 3.2, 3.3, pypy, jython, etc.). Last but not least, the missing killer feature I want is the ability to launch tests on top of Pull Requests, which travis-ci supports.

Then I gave http://wercker.com a shot, but got stuck at the Bitbucket repository selection screen: none were displayed. Maybe because I don't own Pylint's repository, I'm only part of the admin/dev team? Anyway, wercker seems appealing too, though the configuration using yaml looks a bit more complicated than drone.io's, but as I was not able to test it further, there's not much else to say.

So for now the winner is https://drone.io, but the first one allowing me to test on several Python versions and to launch tests on pull requests will be the definitive winner! Bonus points for automating the release process and checking test coverage on pull requests as well.