On Feb 9, 2010, at 8:14 PM, Tony S Yu wrote:
On Feb 9, 2010, at 11:05 PM, Alex Ross wrote:
On Feb 9, 2010, at 8:01 PM, Tony S Yu wrote:
On Feb 9, 2010, at 9:25 PM, Alex Ross wrote:
On Feb 9, 2010, at 6:16 PM, Tony S Yu wrote:
Actually, on my system, I have issues before even calling plt.show(). The example above (w/o plt.show) should quit without showing any sort of plot, but on my system, python/textmate just hangs. The hanging happens regardless of whether or not I call plt.show.
Since both you and Mark (see previous reply) can get around this issue by removing dylib but I can't, either there are two different issues or I have tm_interactive_input.dylib in some as-yet-undiscovered location. So far I've removed the dylib from:
~/Library/Application\ Support/TextMate/Support/lib/ /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
Is this file copied or cached anywhere else? (I've already searched with Finder and the locate command.)
Can you use Activity Monitor to sample the hung process?
Yes, I can. I get back a ridiculously call graph, but I'm not sure if it's actually helpful (but, then again I don't really know what I'm looking at). If it'd be helpful, I could post the full graph somewhere.
Yes, if you could post it that would (could?) be helpful.
This is the same trace I get with the dylib *enabled*, which leads me to believe that you've still got a dylib somewhere. You can make sure it's disabled by setting the variable TM_INTERACTIVE_INPUT_DISABLED=true in TextMate's shell variables preference pane.
TextMate will always use the dylib at $TM_SUPPORT_PATH/lib/tm_interactive_input.dylib. You can find $TM_SUPPORT_PATH by entering “echo $TM_SUPPORT_PATH” in a TextMate document and press CTRL+R to run that line with bash.
If you meant to send me a trace with the dylib enabled, could you also send one with the dylib disabled?
—Alex