Python bindings installer

[GoogleCodeExporter]

Hi David,
The Python bindings installer is useless in the current state as some files 
are missing. Please take a look at 
http://code.google.com/p/ossbuild/source/browse/trunk/Packaging/Win32/Pytho
n/python_bindings.iss?r=397 to see how the bindings should be deployed.
Also, do not use this  naming scheme lib$(var.PREFIX)audio.pyd for python 
binaries.
In Python you will do:

import pygst
pygst.require('0.10')
import gst.audio

That will look for  gst-0.10/gst/audio.pyd

I'm fixing it.

Original issue reported on code.google.com by ylatuya on 21 Jan 2010 at 11:01

[GoogleCodeExporter]

I suppose this brings up a few issues...

If there's a need to brand our libs for compliance w/ developer's wishes, 
should we 
alter the bindings as well?

I made initial in-roads into changing the .net bindings to use the branded 
dll's, 
but it's middle-of-the-road right now.

Original comment by david.g.hoyt on 21 Jan 2010 at 5:20

[GoogleCodeExporter]

I don't see why we should have to change the python dynamic modules names. If 
the
binaries are not installed in the Python path, you won't be able to import them 
using
'import pygst'. 
A way to  'brand' it, is to rename the folder gst-0.10 to gst-ossbuild-0.10. 
This way
developers will have to do:
import pygst
pygst.require('ossbuild-0.10')

Any way, as a Python developer, I don't recommend it. It's preferable being 
able to
switch bindings by changing the python path than having to modify imports in 
the code

Original comment by ylatuya on 21 Jan 2010 at 5:41

[GoogleCodeExporter]

We should follow your recommendations then.

Original comment by david.g.hoyt on 21 Jan 2010 at 5:49

[GoogleCodeExporter]

I believe this is fixed in the trunk.

Original comment by david.g.hoyt on 6 Feb 2010 at 9:08

• Changed state: Fixed