[bitbake-devel] [Openembedded-architecture] Python 3 for Bitbake
Philip Balister
philip at balister.org
Thu May 5 12:13:18 UTC 2016
On 05/04/2016 05:29 PM, Mark Hatle wrote:
> On 5/4/16 3:56 AM, Richard Purdie wrote:
>> My proposal is we decide to have the flag day, we queue up the patches
>> on a python3 branch both in oe-core and bitbake, then we switch when we
>> get successful autobuilder builds. I'd ideally like to do this quite
>> soon and get one with it (within a few weeks), leaving plenty of time
>> to handle issues and the other changes planned for this release cycle
>> and give other layers time to adapt.
>>
>> I will likely push things so the basics in the core work, I'll then
>> need help for things like toaster, the QA framework, the supporting
>> tools (devtool, recipetool and so on).
>>
>> Does anyone object to this?
>
> I think this is a good plan. Flag day, and switch.
>
> Question, do we need any type of identifier in layers to say they're "python3"
> compatible or not?
Layers that are python2 will need krogoth branches. I'd expect master
branches to follow oe-core/master and jump to python3.
Philip
>
> I'd hate for someone to bring in a layer and find it doesn't work, without
> understanding WHY it doesn't work.
>
> Alternative would be to change the 'python' identifier to 'python3'.. Then if
> 'python' is parsed, we error?
>
> --Mark
>
>> Cheers,
>>
>> Richard
>>
>>
>>
>> _______________________________________________
>> Openembedded-architecture mailing list
>> Openembedded-architecture at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
>>
>
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
>
More information about the bitbake-devel
mailing list