Subject: Re: [ecasound] ecanative.py - testing needed
From: janne halttunen (jhalttun_AT_pp.htv.fi)
Date: Wed Mar 12 2003 - 00:03:46 EET
On Tue, 11 Mar 2003 03:47:05 +0200 (EET)
Kai Vehmanen <kai.vehmanen_AT_wakkanet.fi> wrote:
> I've just committed Janne's ecanative.py implementation to CVS, along with
> changes to configure.in. Few points:
>
> - {eci,pyeca,ecanative}.py are installed if python interpreter
> is found
Sorry for the inconvinience, but I changed the module name: from ecanative.py to ecacontrol.py.
http://www.pp.htv.fi/jhalttun/ecacontrol.tar.gz
I think this is more intuitive name. Hope this gets to the distribution before 2.2.2.
(note: setup.py script is not present in this package)
> - pyecasound.so is compiled and installed only if
> a) --enable-pyecasound is specified, and
> b) python devel headers and libs are found
>
> Testing results are very welcome. I'd like to release 2.2.2 before
> ladmeet03 (in other words deadline is Wednesday).
Ok, the new (native python) version works according to my limited testing with curses app ecasetupedit, so that corner is somewhat explored.
What I'm especially interested of hearing about is:
* python version 1.5 - does it work well?
* cleanup - do you see dead ecasound processes left behind?
* hangups & hangup handling - please report these
janne
This archive was generated by hypermail 2b28 : Tue Mar 11 2003 - 23:57:36 EET