Toshio Kuratomi 9f7b0dfc30 Remove automatic use of system six ... * Enable the pylint no-name-in-module check. Checks that identifiers in imports actually exist. When we do this, we also have to ignore _MovedItems used in our bundled six. This means pylint won't check for bad imports below ansible.module_utils.six.moves but that's something that pylint punts on with a system copy of six so this is still an improvement. * Remove automatic use of system six. The exec in the six code which tried to use a system library if available destroyed pylint's ability to check for imports of identifiers which did not exist (the no-name-in-module check). That test is important enough that we should sacrifice the bundling detection in favour of the test. Distributions that want to unbundle six can replace the bundled six in ansible/module_utils/six/__init__.py to unbundle. however, be aware that six is tricky to unbundle. They may want to base their efforts off the code we were using: 2fff690caa/lib/ansible/module_utils/six/__init__.py * Update tests for new location of bundled six Several code-smell tests whitelist the bundled six library. Update the path to the library so that they work. * Also check for basestring in modules as the enabled pylint tests will also point out basestring usage for us.		2017-07-25 15:58:23 -07:00
..
compile	Docs how to test (2nd) (#24094)	2017-04-28 09:08:26 +01:00
integration	cloud: cs_user: add feature keys handling (#27285)	2017-07-25 18:07:58 +02:00
results	Create bot friendly sanity output. (#22381)	2017-03-07 14:59:50 -08:00
runner	Remove automatic use of system six	2017-07-25 15:58:23 -07:00
sanity	Remove automatic use of system six	2017-07-25 15:58:23 -07:00
units	Remove automatic use of system six	2017-07-25 15:58:23 -07:00
utils	Optimize running of CI cloud integration tests.	2017-07-14 22:28:14 -07:00