I would prefer disabling Python in csound5gui until the 5.02 release,
and trying to get it working in 5.03; delaying the 5.02 release does
not significantly increase the amount of time available for working on
these issues, particularly considering that there will be no CVS at
least until the end of this week, and the sources cannot be synchronized
making development much harder. On the other hand, there is plenty of
time until 5.03, as it probably will not be released before July.

By the way, when loading the Python module dynamically, it should also
be checked if the GUI and the csnd module use the same floating point
type (for example, I build most binaries with both floats and doubles,
but the interfaces are 64-bit only).

On Wednesday 10 May 2006 22:26, Michael Gogins wrote:

> This is another reason to delay the next release. My options seem
> to be (a) remove Python from csound5gui and keep it in CsoundVST,
> which means csound5gui always works and uses Python if it's available
> but CsoundVST won't work if you don't install Python, or (b) get
> Python in csound5gui working and remove it from CsoundVST, which
> means both binaries will work whether or not Python is present, and
> people who want to Python-script Csound switch from CsoundVST to
> csound5gui, which can have better editors and let you edit orc and
> script at the same time. What remains to do in csound5gui is create
> a Python performance thread.         


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net