provide a build of the gstreamer bindings for python 2.7

[GoogleCodeExporter]

I have documented the build problems I encountered in this upstream bug: 
[https://bugzilla.gnome.org/show_bug.cgi?id=634493]

Original issue reported on code.google.com by tot...@gmail.com on 1 Dec 2010 at 12:12

[GoogleCodeExporter]

This should be fixed in r945 :)

Original comment by ylatuya on 9 Dec 2010 at 10:22

• Changed state: Fixed

[GoogleCodeExporter]

The beta SDK released a month later still does not have python 2.7 bindings.
Is this intentional?
Also the project file in python-gst is for VS 2003 and Python 2.4...
Can we have something a bit more up to date?

Original comment by tot...@gmail.com on 28 Feb 2011 at 1:25

[GoogleCodeExporter]

No -- these projects (in r945) weren't added to the main solution I don't think 
(I haven't double checked, though) and probably weren't added to the installer 
either.

ylatuya: can you do that?

Original comment by david.g.hoyt on 28 Feb 2011 at 1:57

[GoogleCodeExporter]

ylatuya: nevermind, I went ahead and did it (r984). 

I'll be posting a new beta with the python 2.7 bindings in the SDK. We won't be 
changing the default python version so close to a release, but in the next one 
we can update to v2.7 being the default or perhaps even move on up to v3.2 if 
the bindings work correctly -- mainly because of a stable ABI and we can get 
rid of the python version-specific projects that are a pain to maintain. Of 
course, community input is always desired.

Please let us know if these bindings work correctly for you.

Original comment by david.g.hoyt on 3 Mar 2011 at 8:18

[GoogleCodeExporter]

Great! Thank you (can you re-post here when it's there so I will know about it 
please) . I've had to disable pygst support in my app as I started building 
everything with python 2.7 only on win32.

As for python 3.x, I understand the need to provide support for 3.x bindings, 
but you will find that many applications (mine included) simply cannot move to 
3.x (not yet anyway), so we will need 2.7 bindings supported for a while still.

Original comment by tot...@gmail.com on 3 Mar 2011 at 8:31

[GoogleCodeExporter]

The new beta is available for download if you hadn't already discovered it by 
now.

I know there's issues migrating from 2.x to 3.x, but for those of us having to 
build/maintain language bindings, 3.2+ (not anything < 3.2) is very appealing.

I suppose we'll split the difference -- remove 2.5/2.6, add 3.2, keep 2.7, and 
make the default 2.7 (for now). Thoughts?

Original comment by david.g.hoyt on 3 Mar 2011 at 9:58

[GoogleCodeExporter]

That seems sensible, moving to 2.7 is pretty easy from 2.5 and 2.6.

As for moving to 3.2, I think this is going to take a while - you will be doing 
your part by providing the bindings.

You could even make the 3.2 bindings the default to encourage users since this 
seems preferable to you - as long as bindings for 2.7 are still provided.

Original comment by tot...@gmail.com on 3 Mar 2011 at 10:20

[GoogleCodeExporter]

It's certainly preferable to me, but I don't want to be a dictator and ignore 
my constituents. (c: The project is driven by its community, so I want to make 
sure and keep as many people as happy as possible.

Original comment by david.g.hoyt on 4 Mar 2011 at 4:01

[GoogleCodeExporter]

I don't think removing 2.5 and 2.6 is a good idea because some projects might 
still be shipping older versions of python in windows, so I'll keep them.
As for making 3.2 the default version it's definitively too soon and I'll wait 
until the open source world moves towards python 3.x and the big distros like 
Debian start using it.

Original comment by ylatuya on 6 Mar 2011 at 12:54

[GoogleCodeExporter]

Sounds like 2.5 and 2.6 are here to stay (for a while, at least). It is a pain 
to maintain compatibility with multiple python versions all at the same time, 
though. :/

Original comment by david.g.hoyt on 7 Mar 2011 at 12:57