From: "Javier Hernández Antúnez" <jhernandez@emergya.com>
To: linux-hotplug@vger.kernel.org
Subject: Inconsistences using GUdev.Client
Date: Thu, 12 Apr 2012 12:18:41 +0000 [thread overview]
Message-ID: <CABpL_NdACqSWGs+oepbR4KpeDWu5wBseWBKbwSb5mZ3vvpENKA@mail.gmail.com> (raw)
Hi!
I've been porting a python application which uses gudev to use the new
gobject-introspection based bindings, but I encountered an issue. So,
I pulled udev from master and the issue was still there, so I went to
talk with some pygobject developers, and here's a retail of the
conversation.
16:12 < jhernandez> I'm using GUdev with pygobject
16:12 < jhernandez> and, I have some doubts regarding the way I'm using it
16:13 < jhernandez> with the old python-gudev, I was used to do like
this: client = gudev.Client(subsystems)
16:14 < jhernandez> using the gobject introspected bindings, I'm not
able to get my client object like I was used
16:14 < jhernandez> instead, I need to use the gudev.Client.new method
16:16 < jhernandez> should I report this as a bug? or it is my fault?
16:59 < tomeu> all GObjects should be instantiable with g_object_new
16:59 < tomeu> the problem is people doing things in _new_* that
should be done instead in _init or _construct
16:59 < tomeu> jhernandez: it's a bug that should be reported
17:00 < tomeu> (in GUDev)
17:00 < jhernandez> tomeu: ACK
JFYI, the full conversation log is here [1]
I think the final decision on this is up to udev/gudev developers, and
I'll try (with some help) to provide a patch if it is really needed.
My devel environment consists in:
- openSUSE 12.1 + Official updates
- udev pulled from master (182)
Best regards!
[1]: http://pastebin.com/js7rKh3J
--
Javier Hernández Antúnez
<jhernandez@emergya.com>
next reply other threads:[~2012-04-12 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 12:18 Javier Hernández Antúnez [this message]
2012-04-12 12:59 ` Inconsistences using GUdev.Client Javier Hernández Antúnez
2012-04-12 15:32 ` David Zeuthen
2012-05-05 21:42 ` Martin Pitt
2012-05-06 12:55 ` Martin Pitt
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=CABpL_NdACqSWGs+oepbR4KpeDWu5wBseWBKbwSb5mZ3vvpENKA@mail.gmail.com \
--to=jhernandez@emergya.com \
--cc=linux-hotplug@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).