That's brilliant - thankyou so much! I don't know if this will help, but I checked out all the bundles and the support folder, then tried running my problematic script. It now works fine without having to set the environment variable.

On 2 Apr 2009, at 17:09, Alex Ross wrote:

On Mar 12, 2009, at 3:17 AM, Michael Dewar wrote:

So the new version of textmate broke Pymate for me in some way that
no-one's been able to figure out see:
* http://www.nabble.com/Python-Bundle-Problem---uncaught-signal--11-after...-td22118564.html
* http://www.nabble.com/support-td22230035.html

Is there a way I can get the previous version of textmate, which
worked fine?

Hey Michael… sorry this has been taking so long to rectify.
Yesterday I applied some patches to Executor; while they won't *fix*
your specific problem, they should help you work around it. You can
set the environment variable TM_INTERACTIVE_INPUT_DISABLED in
TextMate' preferences. This disables the loading of a special dylib
that is likely causing problems with scipy.

Please note, you'll have to do an svn checkout of the TextMate bundles
and Support folder. These changes haven't made it into a cutting-edge
or minor release yet.

—Alex

_______________________________________________
textmate mailing list
textmate@lists.macromates.com
http://lists.macromates.com/listinfo/textmate