python3: upgrade to 3.7.2

2019-02-08T10:57:19+00:00

I took the same approach as the recent perl upgrade: write recipe from scratch, taking the pieces from the old recipe only when they were proven to be necessary. The pgo, manifest and ptest features are all preserved. New features: - native and target recipes are now unified into one recipe - check_build_completeness.py runs right after do_compile() and verifies that all optional modules have been built (a notorious source of regressions) - a new approach to sysconfig.py and distutils/sysconfig.py returning values appropriate for native or target builds: we copy the configuration file to a separate folder, add that folder to sys.path (through environment variable that differs between native and target builds), and point python to the file through another environment variable. There were a few other patches where it was difficult to decide if the patch is still relevant, and how to test that it works correctly; please add those as-needed by testing the new python. (From OE-Core rev: 02714c105426b0d687620913c1a7401b386428b6) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

python3: don't use runtime checks to identify float endianism

2018-09-10T11:13:06+00:00

Python uses AC_RUN_IFELSE to determine the byte order for floats and doubles, and falls back onto "I don't know" if it can't run code. This results in crippled floating point numbers in Python, and the regression tests fail. Instead of running code, take a macro from autoconf-archive which compiles C with a special double in which has an ASCII representation, and then greps the binary to identify the format. (From OE-Core rev: 1781b87ae0765c1867da2fa8c56bf988b4e84405) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

linux/poky.git/meta/recipes-devtools/python/python3/float-endian.patch, branch mickledore-next

python3: upgrade to 3.7.2

python3: don't use runtime checks to identify float endianism