Hi Martin,
as probably also found in the archives, this is obviously caused by
flext-based externals built with different (older) flext versions.
It's a good idea to update your other externals, apart from pyext, too.
greetings,
Thomas
Am 02.04.2007 um 03:05 schrieb Martin Peach:
I was
hi Martin, Thomas
I tried to get the py ext to work many times, now I finally made it work
, on winxp and pd 040-2 vanilla. Pyext from
http://g.org/ext/py/py-bin-0.2.0-pd-win.zip, python 2.4.4..
Follow the instructions in the readme.txt
If you dont set the path to the scripts, the strange
Hi,
BTW the sig examples are not working, but the rest are OK.
Not working in which way?
I'm not really sure if it's a good idea to use signals in Python
anyway, because it's a real CPU-hog.
greetings,
Thomas
--
Thomas Grill
http://g.org
Thomas Grill skrev:
Hi,
BTW the sig examples are not working, but the rest are OK.
Not working in which way?
first
they just crash pd
then I installed numpy-1.0.1.win32-py2.4.exe
now I can see the patch but also the wincrashmenu
I'm not really sure if it's a good idea to use signals in
I was hoping to try python with pd but ran into this, which has been
mentioned before:
http://lists.puredata.info/pipermail/pd-list/2006-11/044535.html
I find that the [pyext]s occasionally do appear but usually they don't.
It doesn't seem to matter if they are top level or not.
This is on
Soemthing similar was happening with cyclone objects. It turned out
to be because it was compiled with MinGW without the -mms-bitfields
flag.
.hc
On Apr 1, 2007, at 9:05 PM, Martin Peach wrote:
I was hoping to try python with pd but ran into this, which has been
mentioned before:
