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 oe-core was impacted by this, as
far as I see, but if GNU radio isn't building properly anymore, then
copy-paste the error, and we'll work out a solution.
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.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
