Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id A4F84E00A94; Thu, 27 Sep 2018 01:56:11 -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=-4.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_MED 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] * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [134.102.50.17 listed in list.dnswl.org] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 HTML_MESSAGE BODY: HTML included in message X-Greylist: delayed 982 seconds by postgrey-1.32 at yocto-www; Thu, 27 Sep 2018 01:56:09 PDT Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C615CE00A54 for ; Thu, 27 Sep 2018 01:56:09 -0700 (PDT) Received: from uni-bremen.de (webmail-1.zfn.uni-bremen.de [134.102.50.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id EB1E9275C0 for ; Thu, 27 Sep 2018 10:39:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-bremen.de; s=dkim; t=1538037585; bh=RA9IpoEcU2jpCMHSSO/GcR/aYbPjcxOrrgSd/GM+3/U=; h=To:Date:From; b=LwE22UxRLgXge/09ZDapu25NPUe2Bp71PhbnuNrutsaDQBPEE7raK/4gjqyLpPEQw RTG/hLoFQ/q5kASZF57Lf95T+UnbUY1noA+x9NdPbdw1ouljPdicnez+nu60CvauHr /2b5tVggNButS3EC4gM7DUIsWPXgFRIC/T3b7Kug= To: yocto@yoctoproject.org Date: Thu, 27 Sep 2018 10:39:43 +0200 Message-ID: <001401d4563d$a32ce810$e986b830$@uni-bremen.de> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdRWO95KieAgVHqWRH2MapDqeTGNDg== User-Agent: Horde Application Framework 5 From: Shantanoo Desai Subject: Strange behavior with python recipe 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: Thu, 27 Sep 2018 08:56:11 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01D4564E.66B73EB0" Content-Language: de ------=_NextPart_000_0015_01D4564E.66B73EB0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello all, I am working with the following: . Hardware: Phytec-imx6-Mira Development board . Branch: krogoth . Bitbake Version: 1.30 . Workflow tool: devtool . Build Env: Debian 9.4 server I want to use the pynmea2 and influxdb-python modules on the embedded board for application development. I added them using devtool and the recipes were created accordingly. I added the necessary RDEPENDS to the recipes and structured them to the meta-python layer i.e. pynmea2.inc and pynmea2_1.7.1.bb (similar for influxdb-python) My application needs to be with python3 hence in the recipes I added `inhert setuptools3 pypi` so that it builds for python3. I added these recipes in my `local.conf` file. Strangely, there is no `datetime` module available in the python3 shell when I import these modules on the hardware. This same `datetime` module is however available on python2 shell. I explicitly added the `python3-datetime` in the `local.conf` file but still the module is unavailable on hardware. Links to necessary files and query: Stackexchange Query: https://stackoverflow.com/questions/52519565/no-module-named-datetime-in-pyt hon3-when-creating-a-recipe-for-yocto-but-datet/52528150#52528150 Github Gists of the recipes: https://gist.github.com/shantanoo-desai/fc00836d399f8592a30efe1ec9c56213 I am not sure why isn't this python3-datetime module available on board even though I have explicitly mentioned it in the RDEPENDS and IMAGE_INSTALL_append ? Any help would be appreciated. (First time poster in the mailing-list but willing to learn the right etiquettes for asking queries here!) Regards, Shan ------=_NextPart_000_0015_01D4564E.66B73EB0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello all,

 

I am working with the = following:

 

·       = Hardware: = Phytec-imx6-Mira Development board

·       = Branch: = krogoth

·       = Bitbake Version: = 1.30

·       = Workflow tool: = devtool

·       = Build Env: Debian 9.4 = server

 

I want to use the pynmea2 and influxdb-python modules on = the embedded board for application development. I added them using = devtool and the recipes were created = accordingly.

I added the necessary RDEPENDS to the recipes and = structured them to the meta-python layer i.e. pynmea2.inc and = pynmea2_1.7.1.bb (similar for influxdb-python)

 

My application needs to be with = python3 hence in the recipes I added `inhert setuptools3 pypi` so that = it builds for python3. I added these recipes in my `local.conf` = file.

 

Strangely, there is no `datetime` module available in the = python3 shell when I import these modules on the hardware. This same = `datetime` module is however available on python2 = shell.

 

I explicitly added the `python3-datetime` in the = `local.conf` file but still the module is unavailable on = hardware.

 

Links to necessary files and query:

 

Stackexchange Query: https://stackoverflow.com/questions/52519565/no-module-named-datetim= e-in-python3-when-creating-a-recipe-for-yocto-but-datet/52528150#52528150=

Github = Gists of the recipes: https://gist.github.com/shantanoo-desai/fc00836d399f8592a30efe1e= c9c56213

 

I am not sure why isn’t this python3-datetime module = available on board even though I have explicitly mentioned it in the = RDEPENDS and IMAGE_INSTALL_append ?

 

Any help would be appreciated. = (First time poster in the mailing-list but willing to learn the right = etiquettes for asking queries here!)

 

Regards,

Shan

------=_NextPart_000_0015_01D4564E.66B73EB0--