From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] python-rtslib-fb: new package
Date: Wed, 17 Sep 2014 17:29:23 +0200 [thread overview]
Message-ID: <20140917172923.11d303c2@free-electrons.com> (raw)
In-Reply-To: <20140917172111.570fa8c1@grp-cvubrugier>
Dear Christophe Vu-Brugier,
On Wed, 17 Sep 2014 17:21:11 +0200, Christophe Vu-Brugier wrote:
> The only "issue" I face at the moment is with pyparsing. I get an
> ImportError when I try to import this module from Python 3. I think the
> module is correctly installed: I compared the installation in Buildroot
> and in a virtualenv and the only difference I see is that a
> "pyparsing.py" file is installed in "site-packages/" in my virtualenv.
>
> It is expected since BR2_PACKAGE_PYTHON3_PYC_ONLY is selected. If I
> select BR2_PACKAGE_PYTHON3_PY_PYC instead, then importing the pyparsing
> module works.
>
> I don't know how to properly fix this. What would you suggest?
Aah, yes, sorry, not your fault. There is an issue with Python 3 and
external modules in the BR2_PACKAGE_PYTHON3_PYC_ONLY case, caused by
PEP 3147. There is a patch pending at
http://patchwork.ozlabs.org/patch/373082/ to solve this, but I'm not
really happy with the proposed solution, and I wanted to investigate
this a bit more. Which I've started to do, but of course didn't had
enough time to come to a conclusion.
For the time being, either apply the patch mentioned above, or use
BR2_PACKAGE_PYTHON3_PY_PYC.
Sorry again :/
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-17 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 11:39 [Buildroot] [PATCH 0/6] targetcli-fb: new package Christophe Vu-Brugier
2014-09-17 11:39 ` [Buildroot] [PATCH 1/6] python, python3: add patch to prevent distutils from adjusting the shebang Christophe Vu-Brugier
2014-09-17 11:39 ` [Buildroot] [PATCH 2/6] python-urwid: new package Christophe Vu-Brugier
2014-09-17 11:59 ` Thomas Petazzoni
2014-09-17 11:39 ` [Buildroot] [PATCH 3/6] python-rtslib-fb: " Christophe Vu-Brugier
2014-09-17 12:00 ` Thomas Petazzoni
2014-09-17 13:13 ` Christophe Vu-Brugier
2014-09-17 13:15 ` Thomas Petazzoni
2014-09-17 15:21 ` Christophe Vu-Brugier
2014-09-17 15:29 ` Thomas Petazzoni [this message]
2014-09-17 20:00 ` Jerzy Grzegorek
2014-09-18 7:39 ` Christophe Vu-Brugier
2014-09-17 11:39 ` [Buildroot] [PATCH 4/6] python-configshell-fb: " Christophe Vu-Brugier
2014-09-17 12:03 ` Thomas Petazzoni
2014-09-17 11:39 ` [Buildroot] [PATCH 5/6] targetcli-fb: " Christophe Vu-Brugier
2014-09-17 11:39 ` [Buildroot] [PATCH 6/6] targetcli-fb: add sysv initscript Christophe Vu-Brugier
2014-09-17 12:12 ` Thomas Petazzoni
2014-09-17 13:19 ` Christophe Vu-Brugier
2014-09-17 13:21 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140917172923.11d303c2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.