Re: [OE-core] [PATCH 1/5] python3: split python target configuration into own class

2020-11-15 Thread akuster
On 11/13/20 11:48 AM, Alexander Kanavin wrote: > Setting _PYTHON_SYSCONFIGDATA_NAME in python3native class globally was > problematic as it was leaking into host python environment, which > was causing tracebacks depending on host distro and action > (typically anything involving importing

Re: [OE-core] [PATCH 1/5] python3: split python target configuration into own class

2020-11-14 Thread Alistair Francis
On Fri, Nov 13, 2020 at 11:49 AM Alexander Kanavin wrote: > > Setting _PYTHON_SYSCONFIGDATA_NAME in python3native class globally was > problematic as it was leaking into host python environment, which > was causing tracebacks depending on host distro and action > (typically anything involving

[OE-core] [PATCH 1/5] python3: split python target configuration into own class

2020-11-13 Thread Alexander Kanavin
Setting _PYTHON_SYSCONFIGDATA_NAME in python3native class globally was problematic as it was leaking into host python environment, which was causing tracebacks depending on host distro and action (typically anything involving importing sysconfig module). The new class sets the variable only in