From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12346] New: Python 3.8/GObject on 2019-11rc2
Date: Sat, 23 Nov 2019 16:47:20 +0000 [thread overview]
Message-ID: <bug-12346-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12346
Bug ID: 12346
Summary: Python 3.8/GObject on 2019-11rc2
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: info at hifiberry.com
CC: buildroot at uclibc.org
Target Milestone: ---
The 201911 release have been upgraded to Python 3.8. However, the included
python-gobject is incompatible with Python 3.8:
Python 3.8.0 (default, Nov 23 2019, 09:12:01)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gobject
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python3.8/site-packages/gobject/__init__.py", line 26, in
<module>
from glib import spawn_async, idle_add, timeout_add, timeout_add_seconds, \
File "/usr/lib/python3.8/site-packages/glib/__init__.py", line 22, in
<module>
from glib._glib import *
SystemError: initialization of _glib raised unreported exception
An alternative to python gobject would be python GI, but this requires
introspection. As far as I understand this is not yet working.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-11-23 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 16:47 bugzilla at busybox.net [this message]
2019-11-27 14:05 ` [Buildroot] [Bug 12346] Python 3.8/GObject on 2019-11rc2 bugzilla at busybox.net
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=bug-12346-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.