Possible inconsistencies between python and C API

[Antonio Ospite]

On Thu, 03 Jan 2019 16:00:59 +0200
Sebastian Dröge <sebastian at centricular.com> wrote:

> On Wed, 2019-01-02 at 13:30 +0100, Antonio Ospite wrote:
> > On Thu, 13 Dec 2018 11:10:02 +0100
> > Antonio Ospite <ao2 at ao2.it> wrote:
> > 
> > > Hi,
> > > 
> > > I wanted to brush up my GStreamer game and I though I'd write some
> > > example elements in python to fixate some concepts without the
> > > distracting C boilerplate.
> > > 
> > 
> > I ended up writing the elements in C, but I would still be interested
> > to have the issues with pyhton bindings fixed, read below for some
> > questions.
> 
> Please create an issue for any API problems (one for each) in
> gst-python:
>   https://gitlab.freedesktop.org/gstreamer/gst-python/issues/new
>
> > > In particular I was writing a demuxer and a parser
> 
> Performance-wise it's not a good idea to write GStreamer elements in
> Python, because of the global interpreter lock. C, C++ and Rust seem
> better choices at this point.
> 

I see, and memory is also less "controllable" from pyhton, but I still
find value in using python for learning and prototyping, so I went
ahead and filed the reports to gst-python.

Thank you,
   Antonio

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?