[gstreamer-bugs] [Bug 549879] gst-python managing sys.argv while it shouldn't

[GStreamer (bugzilla.gnome.org) <bug...@bu...>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=549879

  GStreamer | gst-python | Ver: 0.10.12




------- Comment #13 from George Retsinas  2009-04-18 10:08 UTC -------
(In reply to comment #6)
> The workaround is straight forward : parse sys.argv before calling import gst.
> sys.argv parsing should, after all, be the first thing you do in your
> application/loader.
That is not always true. When we are talking about a simple, one-file
application, what is usually done is modules imported at the start, then go all
the classes and functions and at the end of the file in if __main__ ... goes
the argument parsing and everything else required for initialization.

> the sys.argv arguments *NEED* to be parsed when calling gst_init(). There's no
> way around that, since they will modify the gstreamer initialization.
Is it a must for the application's sys.argv to be parsed? Can't it be skipped
somehow? Replacing it with what is needed, not including the app's sys.argv,
before initializing gstreamer and after initialization, restoring it or
something like that? What I am saying might be really crazy, I have never
looked at gst-python/gstreamer's source code to see how all this is handled, I
am just throwing some ideas.

(In reply to comment #7)
> Couldn't you make the call to gst_init() mandatory for the client using the
> bindings? Many modules do such a thing, take pyGTK for example.
That could be a way to resolve the case mentioned above in a proper way.
Especially the way Michael Smith proposed so there is no backwards
compatibility breakage.

As of the other points of Michael Smith and Tobias Mueller, I agree with all of
them.

Anyway, I think you have made your point of view clear, so maybe this bug
should be marked wontfix?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=549879.