Hello,
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...-t... * http://www.nabble.com/support-td22230035.html
Is there a way I can get the previous version of textmate, which worked fine?
Cheers,
Mike Dewar
On 12 Mar 2009, at 11:17, Michael Dewar wrote:
So the new version of textmate broke Pymate for me [...]
Is there a way I can get the previous version of textmate, which worked fine?
http://download-b.macromates.com/TextMate_1.5.7.dmg
Or you can try to checkout an older version of the Python bundle from http://svn.textmate.org/trunk/
On Thu, Mar 12, 2009 at 6:17 AM, Michael Dewar mikedewar@gmail.com wrote:
Hello,
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...-t... * http://www.nabble.com/support-td22230035.html
Signal 11 is a segfault, which means Python is accessing memory outside of where it should. Python should _never_ do this, and the Python developers consider it a bug if the interpreter crashes.
That said, I don't understand why it happens only when running from TM, but clearly something is different when you are running Python in the TM environment than your shell (Terminal) environment.
So, a few things:
1) Open a new TextMate window and run Text -> Filter Through Command…. Enter "env | sort" as the command, and select Input: None, Output: Replace Document. Then cut and paste the results for us.
2) Similarly, run "env | sort" in a Terminal window and cut and paste those results as well.
3) Since Python is crashing, there is a crash log. Look in ~Library/Logs/CrashReporter and send us the most recent python interpreter crash log.
4) The fact that `which python` returns "/Library/Frameworks/Python.framework/Versions/Current/bin/python" is odd. Apparently you have "/Library/Frameworks/Python.framework/Versions/Current/bin" in your PATH before /usr/bin. Just out of curiosity, what does ls -l /usr/bin/python show?
5) Does the crash only happen when you import scipy? How about a simple script such as:
#!/usr/bin/python import sys print sys.version
Will that run properly from within TextMate?
j.
On Sat, Mar 14, 2009 at 3:52 PM, Jay Soffian jaysoffian@gmail.com wrote:
So, a few things:
Here's one more thing to try:
$ touch "$HOME/Application Support/TextMate/bash_init.sh"
If that doesn't clear things up, remove this file, assuming you didn't have it there before.
This will prevent TM from parsing your $HOME/.bash* profile, which in my experience causes more trouble than it solves. (TM attempts to replicate your Terminal environment by doing this, but I have a bunch of customizations in my Terminal environment that I don't want when I run code from within TM.)
j.
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...-t...
- 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
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.
Thanks again,
Mike Dewar
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...-t...
- 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
- - - Dr Michael Dewar School of Informatics The University of Edinburgh (+44)131 6503084 http://homepages.inf.ed.ac.uk/mdewar1/
On Apr 2, 2009, at 1:29 PM, mike dewar wrote:
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.
It does!? Cool. :)
—Alex
One more little thing - at work on a different computer I do need to set the environment variable to get things working. After I do this it all works again perfectly. Thanks again,
Mike
On 2 Apr 2009, at 22:23, Alex Ross wrote:
On Apr 2, 2009, at 1:29 PM, mike dewar wrote:
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.
It does!? Cool. :)
—Alex
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Apr 3, 2009, at 12:32 AM, Michael Dewar wrote:
One more little thing - at work on a different computer I do need to set the environment variable to get things working. After I do this it all works again perfectly. Thanks again,
The only problem with TM_INTERACTIVE_INPUT_DISABLED is Executor does not load the library that captures reads and pops up the little dialog.
—Alex
On Apr 3, 2009, at 8:04 AM, Alex Ross wrote:
On Apr 3, 2009, at 12:32 AM, Michael Dewar wrote:
One more little thing - at work on a different computer I do need to set the environment variable to get things working. After I do this it all works again perfectly. Thanks again,
The only problem with TM_INTERACTIVE_INPUT_DISABLED is Executor does not load the library that captures reads and pops up the little dialog.
Reads of stdin, I should have said.
-
Alex Ross -
Allan Odgaard -
Jay Soffian -
Michael Dewar -
mike dewar