From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: python3 dbus
Date: Wed, 2 Dec 2015 17:39:38 +0200 [thread overview]
Message-ID: <565F10BA.9060006@linux.intel.com> (raw)
In-Reply-To: <C9B171200FE9514799693A59F76A8F1501A0949293@AEP-EXCH-UK-01.ULTRA-AEP.COM>
On 12/02/2015 05:26 PM, Chris Trobridge wrote:
> I have a dbus-based service written in python3 that I want run on a
> Yocto system.
>
> I can run python3 and have patched a few python module recipes to
> python3 but the big outstanding issue is dbus, and gi.repository.GObject
> in particular.
>
> I can see various discussions about keeping this up to date on python2
> (meta-gir).
>
> I would like some advice on whether I would be better off back-porting
> the python3 service to 2.7 (which would be disappointing but not a major
> undertaking) or whether it would be reasonable to modify the existing
> python 2.7 dbus/gobject recipes to python3.
>
> I am tending to back-porting to 2.7 but I am not 100% confident that
> dbus/gobject works with either version of python in Yocto?
Work to integrate gobject introspection directly to oe-core is ongoing
and we aim to have it in 2.1 release. You can find the current patches here:
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/gobject-introspection-experimental
The introduction is here:
http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113390.html
Do give it a try.
Alex
prev parent reply other threads:[~2015-12-02 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 15:26 python3 dbus Chris Trobridge
2015-12-02 15:39 ` Alexander Kanavin [this message]
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=565F10BA.9060006@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.