>> This is because python3-config does not contain the version within >> itself, >> it reports the version of the python interpreter that it is run with. So >> NOTABUG. > > If its supposed to report the version of python pack its coming with > and not the interpreter its run with > then how do you decide its not a behavior change ?
Apologies for being terse. I should've explained that when building recipes that make use of this script, it will be run with the native python (instead of host python) because native python will come first in the PATH, and so the version reported will be correct, because native python will match target python. This is set up in pythonnative.bbclass for python 2, and in python3native.bbclass for python 3. > Lets keep the semantics as they were. I am perfectly fine to revert to > python 3.4 if thats what it takes. We *are* keeping semantics as they were with this patch. Python 3.4 defaults to this script, python 3.5 changes python-config to the broken shell-based rewrite. This patch reverts back to the 3.4 behaviour. Alex -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
