From 93925f7875197e08b9e91019096c196bac2f0e3f Mon Sep 17 00:00:00 2001 From: Tim Orling Date: Wed, 4 May 2016 19:32:54 -0700 Subject: scripts/oe-buildenv-internal: allow experimental python3 support (From OE-Core rev: 06b91103915f73d5b5b2001f76874c73f1d88007) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie --- scripts/oe-buildenv-internal | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/scripts/oe-buildenv-internal b/scripts/oe-buildenv-internal index e04db0398d..55358fbae3 100755 --- a/scripts/oe-buildenv-internal +++ b/scripts/oe-buildenv-internal @@ -35,17 +35,19 @@ fi # can offer a meaningful error message. py_v3_check=$(/usr/bin/env python --version 2>&1 | grep "Python 3") if [ -n "$py_v3_check" ]; then - echo >&2 "Bitbake is not compatible with python v3" - echo >&2 "Please set up python v2 as your default python interpreter" - return 1 + #echo >&2 "Bitbake is not compatible with python v3" + #echo >&2 "Please set up python v2 as your default python interpreter" + #return 1 + echo >&2 "Experimental python v3 support" + py_v3="True" fi unset py_v3_check # Similarly, we now have code that doesn't parse correctly with older # versions of Python, and rather than fixing that and being eternally # vigilant for any other new feature use, just check the version here. -py_v26_check=$(python -c 'import sys; print sys.version_info >= (2,7,3)') -if [ "$py_v26_check" != "True" ]; then +py_v26_check=$(python -c 'import sys; print(sys.version_info >= (2,7,3))') +if [ "$py_v26_check" != "True" ] && [ "$py_v3" != "True" ]; then echo >&2 "BitBake requires Python 2.7.3 or later" return 1 fi -- cgit v1.2.3-54-g00ecf