summaryrefslogtreecommitdiff
path: root/framework/test/glsl_parser_test.py
diff options
context:
space:
mode:
authorDylan Baker <baker.dylan.c@gmail.com>2016-01-04 16:42:45 -0800
committerDylan Baker <baker.dylan.c@gmail.com>2016-02-08 12:29:33 -0800
commitf41158915be47daae8bcf4c7afd54bec577f9454 (patch)
tree18b6aa319c6fbbdd3ffcdbb68196054be70720e8 /framework/test/glsl_parser_test.py
parent8c3bb871120f81b7c57b214ee2771184060a4d6b (diff)
python: use future print, division, and absolute_import
These are the three python3 like behaviors that piglit should rely on. The only other applicable future import is unicode_literals. Although my plan is to use unicode_literals, that will actually cause behavioral changes in some cases, where these cause minimal changes to the code. Piglit will not be targeting < 3.2, they are old, unsupported, and have fewer features than 2.7. Piglit now has division (using / as floating division, and // as integer division), print as a function (rather than a statement), and absolute import, which changes the way import works when there's a conflict between a local import and a system wide one. Absolute import makes more sense, and copies the behavior of python 3 Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com> Acked-by: Jose Fonseca <jfonseca@vmware.com>
Diffstat (limited to 'framework/test/glsl_parser_test.py')
-rw-r--r--framework/test/glsl_parser_test.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/framework/test/glsl_parser_test.py b/framework/test/glsl_parser_test.py
index e17fd64bc..da223fbf3 100644
--- a/framework/test/glsl_parser_test.py
+++ b/framework/test/glsl_parser_test.py
@@ -21,7 +21,7 @@
""" This module enables the running of GLSL parser tests. """
-from __future__ import print_function, absolute_import
+from __future__ import absolute_import, division, print_function
import os
import re