From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 09506E00C76; Fri, 8 Apr 2016 05:16:48 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [192.55.52.115 listed in list.dnswl.org] Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D066EE00BE8 for ; Fri, 8 Apr 2016 05:16:44 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 08 Apr 2016 05:16:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,449,1455004800"; d="scan'208";a="941043322" Received: from kanavin-desktop.fi.intel.com (HELO [10.237.68.161]) ([10.237.68.161]) by fmsmga001.fm.intel.com with ESMTP; 08 Apr 2016 05:16:38 -0700 To: "yocto@yoctoproject.org" References: <57066063.1010008@linux.intel.com> <5706634E.9040106@linux.intel.com> From: Alexander Kanavin Message-ID: <5707A126.4050107@linux.intel.com> Date: Fri, 8 Apr 2016 15:16:38 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: Python GObject Errors on yocto-2.1_M3.rc2 X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 12:16:48 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 04/07/2016 07:58 PM, Chris Trobridge wrote: > http://cgit.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python > > > > Will be fixed by deprecating python 2, of course. > > > > Alex > > Is there a shorter term solution that's generally applicable, like a > separate python3-gobject recipe? In principle, yes - if you need to have pygobject both for 2 and 3 at the same time, you can have two slightly different recipes; but I don't know if it will work. You need to try and see. Alex