Armando Neto b4ad0d19a2 Fix pylint 2.0 return-related violations ... Aiming to support pylint 2.0 some functions and methods must have their return statements updated in order to fix two new violations: - `useless-return` (R1711): Useless return at end of function or method Emitted when a single "return" or "return None" statement is found at the end of function or method definition. This statement can safely be removed because Python will implicitly return None - `inconsistent-return-statements` (R1710): Either all return statements in a function should return an expression, or none of them should. According to PEP8, if any return statement returns an expression, any return statements where no value is returned should explicitly state this as return None, and an explicit return statement should be present at the end of the function (if reachable) Issue: https://pagure.io/freeipa/issue/7614 Signed-off-by: Armando Neto <abiagion@redhat.com> Reviewed-By: Christian Heimes <cheimes@redhat.com>		2018-07-11 10:11:38 +02:00
..
__init__.py	ipapython: move dnssec, p11helper and secrets to ipaserver	2016-11-29 14:50:51 +01:00
client.py	Fix pylint 2.0 return-related violations	2018-07-11 10:11:38 +02:00
common.py	Unified ldap_initialize() function	2018-02-15 18:32:17 +01:00
kem.py	Add absolute_import future imports	2018-04-20 09:43:37 +02:00
service.py	secrets: disable relative-imports for custodia	2017-09-08 15:42:07 +02:00
store.py	Add absolute_import future imports	2018-04-20 09:43:37 +02:00