From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] [PULL REQUEST babeltrace] Python bindings update
Date: Tue, 12 Nov 2013 22:06:41 -0500 [thread overview]
Message-ID: <CA+jJMxsZLrpRXhgZDLqVfGgqjkz6_d=7NKPgRHr5gGc0vmc4TQ@mail.gmail.com> (raw)
Hi all,
Here are some patches to add read support of every CTF type using the
Babeltrace Python bindings. It is now possible to retrieve fields and
access their values using a single get_value() method returning native
Python objects. This is made possible using the work contributed by
one of our GSoC students, Xiaona Han.
These patches also make it possible to generate CTF from Python code,
based on the CTF Writer API that was merged recently.
The patches are available here:
https://github.com/jgalar/babeltrace/commits/bindings/python
7a30a66 Return event fields by field name
db551f2 Remove the unnecessary underscore prefix
4191bcd Support getting the value of enums
3c2ce77 Add a generic get_value() implementation
786207e Support for the sequence type
810a97b Add a python bindings sequence test
3043ee0 Remove Python 2 specific examples
90131a3 Fix: Throw a FieldError exception when get_value() fails
e5a73b9 Add support for floating point fields in the Python bindings
812e668 Add support for variant fields in the Python bindings
3a06891 Add support for structure fields in the Python bindings
cebae8c Fix: Python bindings array access functions write out of bounds
24d5c94 Rename the ctf class to CTFReader
ec8c88d Add CTF Writer Python bindings
033fb0a Add a usage example for the CTF Writer Python bindings
94a6cea Don't generate Python bindings by default
5491476 Expose text arrays the same way as regular arrays
Looking forward to your comments,
J?r?mie
--
J?r?mie Galarneau
EfficiOS Inc.
http://www.efficios.com
next reply other threads:[~2013-11-13 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 3:06 Jérémie Galarneau [this message]
2013-11-13 14:17 ` Mathieu Desnoyers
2013-11-14 9:48 ` [lttng-dev] " Michael Lausch
2013-11-18 16:31 ` Mathieu Desnoyers
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='CA+jJMxsZLrpRXhgZDLqVfGgqjkz6_d=7NKPgRHr5gGc0vmc4TQ@mail.gmail.com' \
--to=jeremie.galarneau@efficios.com \
/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