Re: [OE-core] [PATCH 28/45] swig: move to Python 3

2016-05-30 Thread Alexander Kanavin
On 05/27/2016 04:21 PM, Mike Looijmans wrote: This probably means that projects using Python 2 extensively will be forced to either "freeze" the OE version to the state before the transition or attempt to maintain a "python-2" fork. Not at all. Oe-core will continue to provide python 2 recipes

Re: [OE-core] [PATCH 28/45] swig: move to Python 3

2016-05-27 Thread Mike Looijmans
On 25-05-16 14:45, alexander.kana...@linux.intel.com wrote: I'm trying to get my head around how this change will impact python2 based programs that use swig, such as gnuradio. Does this mean all programs that use swig will need to move to python3 now? Probably. At least nothing in meta-oe or

Re: [OE-core] [PATCH 28/45] swig: move to Python 3

2016-05-26 Thread alexander . kanavin
> > It would be nice to use PACKAGECONFIG to select 2 versus 3 so we can > build sdks that only have python2. This requires a conditional class inherit (pythonnative vs. python3native), which you can't at the moment do with PACKAGECONFIG. If you really need this, make a swig-python2 recipe. Alex

Re: [OE-core] [PATCH 28/45] swig: move to Python 3

2016-05-25 Thread Philip Balister
On 05/25/2016 08:45 AM, alexander.kana...@linux.intel.com wrote: >> I'm trying to get my head around how this change will impact python2 >> based programs that use swig, such as gnuradio. >> >> Does this mean all programs that use swig will need to move to python3 >> now? > > Probably. At least no

Re: [OE-core] [PATCH 28/45] swig: move to Python 3

2016-05-25 Thread alexander . kanavin
> I'm trying to get my head around how this change will impact python2 > based programs that use swig, such as gnuradio. > > Does this mean all programs that use swig will need to move to python3 > now? Probably. At least nothing in meta-oe or oe-core was impacted by this, as far as I see, but if

Re: [OE-core] [PATCH 28/45] swig: move to Python 3

2016-05-24 Thread Philip Balister
I'm trying to get my head around how this change will impact python2 based programs that use swig, such as gnuradio. Does this mean all programs that use swig will need to move to python3 now? Philip On 05/24/2016 07:54 AM, Alexander Kanavin wrote: > Signed-off-by: Alexander Kanavin > --- > me

[OE-core] [PATCH 28/45] swig: move to Python 3

2016-05-24 Thread Alexander Kanavin
Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/swig/swig.inc | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/meta/recipes-devtools/swig/swig.inc b/meta/recipes-devtools/swig/swig.inc index 9da40df..704bb27 100644 --- a/meta/recipes-devtools/swig/swig.inc ++