Interrupting pull with ctrl-C left stale locks that cannot be removed - even with bzr break-lock

[Alexander Belchenko]

John Arbash Meinel пишет:
> Nicholas Allen wrote:
> 
> ...
> 
>> bzr info shows that the working tree, branch and repository are all
>> locked. Now there is no way to use bzr with any branches in the entire
>> repository as I cannot remove the locks.
>>
> 
> Nick and I dug into this today, and found out that the problem is how
> Windows python interacts with non-cmd.exe shells.
> 
> The problem is that terminal I/O is in a weird state on windows. If you
> run a native program (python, psql, etc) in a non-cmd.exe shell (I've
> run into this with rxvt, Nick was running gnome-terminal) then all of
> the output to stdout is just missing.
> 
> For example, just running "python"
> 
> gives you a blank line, and seems like the program is 'hung'. It is
> actually running, but it doesn't seem able to write to the screen.
...
So, it's a Python bug in raw_input() implementation. It hard wired to
cmd.exe terminal window/API.

> Anyway, in the short term, it seems like win32-native bzr won't work
> with fancy shells like gnome-terminal or rxvt do to situations outside
> of our control.

I think we probably need also file a bug in mainstream Python bug tracker...

BTW, when IDLE/PythonWin (GUI IDEs for Python on Windows) runs python
code and come across input/raw_input functions it invoke his own
internal GUI dialog for user prompt.
So it's at least could be overridden.

--
Alexander