bcfg2 - Custom fork of bcfg2 (configuration management)

	Commit message (Collapse)	Author	Age	Files	Lines
*	testsuite: Support for ancient pylint versions	Alexander Sulfrian	2017-03-29	2	-2/+285
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	For Python2.4 and Python2.5 we need very old pylint versions (0.21.x). So we have to work around some bugs: - This adds some ugly monkey patching to backport some bugfixes from newer pylint versions (that does not support Python2.4 anymore). - Another problem is, that pylint-0.24 changed its message IDs. So this translates the new IDs into the older ones, so that the old pylint can match the disabled messages. - The newer version of pylint support more messages and some of the new messages have to be disabled. The old pylint versions have to silently ignore unknown message ids. - The compatible astng version of the old pylint does not support register_transformer, so we need to build out own variant by monkey patching the ASTNGBuilder.
*	testsuite: ExceptionMessageChecker support for old python	Alexander Sulfrian	2017-03-29	1	-3/+8
\|
*	testsuite: support for python-2.7.9maint	Alexander Sulfrian	2015-01-16	1	-0/+17
\| \| \| \| \| \|	pylint could not parse the dynamic assignment of the PROTOCOL_* values in the ssl module (the real values are in the _ssl extension). We dynamically add here the PROTOCOL_* constants we need.
*	testsuite: made pylint tests at least kinda work with pylint 1.0	Chris St. Pierre	2013-12-09	1	-8/+22
\| \| \| \| \| \| \|	They still don't pass, partially due to what appear to be bugs in pylint and partially due to a few new things that pylint is checking for in 1.0, but we don't use pylint 1.0 in travis-ci so i'm not terribly worried about that right now.
*	testsuite: test for exceptions raised without messages	Chris St. Pierre	2012-12-10	2	-0/+35