Vista + Rails 2.0 upgrade => subprocess hangs
Here's a small Python program I use to grab the output from rake: = from subprocess import Popen, PIPE p = Popen(args='c:\\ruby\\bin\\ruby.exe c:\\ruby\\bin\\rake -T', cwd=u'c:\\Users\\ericp\\testing\\file07', shell=True, stdin=None, stderr=PIPE, stdout=PIPE, creationflags=0x800 ); p.wait() data = p.stdout.read() print data = This is on Windows Vista. With Rails 1.2.6 there was no problem. After upgrading to Rails 2.0.1, the program now hangs at the call to the wait() command. If I manually kill the ruby.exe process, I get some of the expected output, but not all of it. I can run the above command from the command-line with no problem. The rake code that Ruby loads did change moving from 1.2.6 to 2.0.1, but subprocess should run the command to completion. I'm not sure what happens yet on XP, or other platforms. I'd like to get this working on Vista, though. Any ideas. Thanks, Eric -- http://mail.python.org/mailman/listinfo/python-list
Re: Vista + Rails 2.0 upgrade => subprocess hangs
> > Your usage of wait() is dangerous. The code can block indefinitely when > the stdout or stderr buffer is full. > > Christian That's what it is. `rake -T` returns more data in Rails 2.0.1 than it did in 1.2.6 -- cross-language breakage logically explained. Thank you, Christian. - Eric -- http://mail.python.org/mailman/listinfo/python-list
Re: Komodo 6, why "Workspace Restore" after every restart?
Komodo always asks you if you want to restore the last workspace when it wasn't shut down cleanly the previous time. The reason for this is that it's possible Komodo ended up in a state where it's hung due to a particular workspace configuration. This question lets you bring up Komodo in a possibly sane configuration instead. Is this the best thing to do? Wouldn't it be better to manually remove a couple of config files, and restart Komodo in a basic but sane configuration? You could make a good case for that, and may I suggest that http://community.activestate.com/forums/komodo-discussion would be a better place to continue this particular discussion? Thanks for bringing up the issue though. Eric Promislow Komodo Developer -- http://mail.python.org/mailman/listinfo/python-list
Re: OT Komodo Edit, line selection gutter is one pixel wide?
On Jul 1, 9:39 am, John Doe wrote: > Is there a way to increase the line selection gutter width? It > seems to be only one pixel wide. In other words... When I single > click on the left side of the line, in order to automatically > select the line, the pointer must be in a precise single pixel > location immediately to the left of the line. Or am I doing > something wrong? > > Thanks. > > By the way... I can see that clicking and dragging to select > multiple lines can be done somewhere in the space of the first > character on the lines, but I am talking about single clicking to > select the single line. You can easily do this with a Komodo macro. First you get a reference to the current buffer like so. In JS: var view = ko.views.manager.currentView; var scimoz = view.scimoz; // the editor In Python code: currentView = components.classes["@activestate.com/koViewService;1"].\ getService(Components.interfaces.koIViewService).currentView view = currentView.QueryInterface(Components.interfaces.koIScintillaView) scimoz = view.scimoz To get the current width of the line-selection margin: oldValue = scimoz.getMarginWidth(2) # Margin #2, width given in pixels To set a new value: scimoz.setMarginWidth(2, newValue) # 4 looks like a good value There is no boundary between the breakpoint margin (1) and the line- selection margin. If you want this behaviour in general, you can write a post-file-open macro that will set the margin after a file is opened. You currently can't write a post-file-open trigger in Python, (see bug http://bugs.activestate.com/show_bug.cgi?id=45265) Hope this helps, Eric Promislow Komodo Team Member -- http://mail.python.org/mailman/listinfo/python-list
