[OpenSIPS-Users] mediaproxy-2.3.5 build dep problem

[Dan Pascu]

On 24 Jul 2009, at 16:21, Jeff Pyle wrote:

> Hello,
>
> When trying to build mediaproxy-2.3.5,
>
> # ./setup.py build
> Traceback (most recent call last):
>  File "./setup.py", line 7, in ?
>    import mediaproxy
>  File
> "/mnt/home/common/mediaproxy-centos/local/mediaproxy-2.3.5/ 
> mediaproxy/__init
> __.py", line 33, in ?
>    dependencies = ApplicationDependencies(**package_requirements)
>  File "/usr/lib/python2.4/site-packages/application/dependency.py",  
> line
> 59, in __init__
>    self.dependencies.extend((PackageDependency(name, version) for  
> name,
> version in sorted(kw.iteritems())))
>  File "/usr/lib/python2.4/site-packages/application/dependency.py",  
> line
> 59, in <generator expression>
>    self.dependencies.extend((PackageDependency(name, version) for  
> name,
> version in sorted(kw.iteritems())))
>  File "/usr/lib/python2.4/site-packages/application/dependency.py",  
> line
> 34, in __init__
>    module = __import__(module_name, fromlist=module_name.rsplit('.',
> 1)[1:])
> TypeError: __import__() takes no keyword arguments
>
>
> I’m upgrading from 2.3.2.  I had python-applications-1.0.9  
> installed, and I
> installed 1.1.4 before trying mediaproxy-2.3.5.  Other than that  
> nothing has
> changed.  Is there some version conflict in python-applications with  
> perhaps
> both of them being there, if they are?  I'm not sure.  I've been  
> spoiled by
> the debian packages, but unfortunately on this CentOS box it's all  
> from
> source.

No, the problem is that you have a python < 2.5 and I didn't check  
that something was not available before python-2.5 when I wrote that  
code in python-application. It'll be fixed with the next release of  
python-application in a few days. In the meanwhile, if you have  
python-2.5 available you can use that and it'll work.

--
Dan