From 462f4a5161185e74432cfe492ab959cc15b12711 Mon Sep 17 00:00:00 2001
From: Petr Viktorin <pviktori@redhat.com>
Date: Tue, 5 Jan 2016 13:39:39 +0100
Subject: Use print_function future definition wherever print() is used

Pylint considers `print` a statement if the __future__ import is
not present, even if it's used like a function with one argument.

Add the __future__ import to files `pylint --py3k` complains about.

https://fedorahosted.org/freeipa/ticket/5623

Reviewed-By: Jan Cholasta <jcholast@redhat.com>
Reviewed-By: Martin Basti <mbasti@redhat.com>
---
 doc/examples/python-api.py | 1 +
 1 file changed, 1 insertion(+)

(limited to 'doc/examples')

diff --git a/doc/examples/python-api.py b/doc/examples/python-api.py
index 8c79dc4ca..0a6eb60ef 100755
--- a/doc/examples/python-api.py
+++ b/doc/examples/python-api.py
@@ -19,6 +19,7 @@
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
 #
 
+from __future__ import print_function
 from ipalib import api
 
 # 1. Initialize ipalib
-- 
cgit