From: simon.marchi@polymtl.ca (Simon Marchi)
Subject: [lttng-dev] [PULL REQUEST babeltrace] Python bindings API refactoring
Date: Fri, 22 Nov 2013 22:29:04 -0500 [thread overview]
Message-ID: <CAFXXi0kr4MnZCzOGWMrUUSstCRT18XJzva=qfBLjoNEv8m8U8g@mail.gmail.com> (raw)
In-Reply-To: <CA+jJMxuaWjcJ7M55TpX=xG00R-VQdm0e0WtMg9M-AxnBQtwGfg@mail.gmail.com>
I'm getting this error when making in bindings/python:
sed "s/BABELTRACE_VERSION_STR/Babeltrace 1.1.1/g" <babeltrace.i.in >babeltrace.i
/usr/bin/swig -python -Wall -I. -I../../include babeltrace.i
babeltrace.i:367: Error: Syntax error in input(1).
make: *** [babeltrace_wrap.c] Error 1
Are you missing a little %pythoncode %{ around class ClockType ?
https://github.com/jgalar/babeltrace/blob/bindings/python/bindings/python/babeltrace.i.in#L361
On 22 November 2013 18:00, J?r?mie Galarneau
<jeremie.galarneau at efficios.com> wrote:
> Hi all,
>
> I received a number of great comments about the Babeltrace Python API
> since my last pull request. These patches, available on my personal
> repository, aim at making the API feel more natural to Python
> developers by using the appropriate language constructs where
> appropriate.
>
> The three "Fix" patches address bugs that were uncovered in the C
> codebase while developing and testing this patch set.
>
> https://github.com/jgalar/babeltrace.git
>
> 2be62ad Python-bindings: Refactor the Context class
> 32de3db Python-bindings: Refactor the TraceHandle class to use properties
> 7740532 Python-bindings: Refactor the Event class
> 10d1b96 Python-bindings: Move the _scopes array out of the Event class
> 99e8489 Python-bindings: Refactor the FieldDecl and EventDecl classes
> 425caab Python-bindings: Move declaration bindings out of the _Definition class
> b5e4875 Fix: Use the bt_iter_set_pos function to set the begin_pos
> 3f8750e Fix: Take the iterator's end position into account
> 35e0cb7 Fix: bt_ctf_field_generic_validate should return < 0 on error
> 810922e Python-bindings: Refactor the CTFWriter API
>
> I think these patches bring us to a point where the bindings/python
> branch could be safely merged into master.
>
> Thanks,
> J?r?mie
>
> --
> J?r?mie Galarneau
> EfficiOS Inc.
> http://www.efficios.com
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2013-11-23 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 23:00 Jérémie Galarneau
2013-11-23 3:29 ` Simon Marchi [this message]
2013-11-23 4:09 ` Simon Marchi
2013-11-23 6:15 ` Jérémie Galarneau
2013-11-23 15:26 ` Mathieu Desnoyers
2013-11-23 21:30 ` [lttng-dev] [PATCH babeltrace python/bindings] Python-bindings fix: outdated dist target babeltrace.i Jérémie Galarneau
2013-11-24 1:31 ` Mathieu Desnoyers
2013-11-28 18:19 ` [lttng-dev] [PATCH babeltrace python/bindings] Python-bindings fix: Out of tree build fails to find babeltrace.i Jérémie Galarneau
2013-11-29 6:21 ` 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='CAFXXi0kr4MnZCzOGWMrUUSstCRT18XJzva=qfBLjoNEv8m8U8g@mail.gmail.com' \
--to=simon.marchi@polymtl.ca \
/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