Thanks for your comments, and thanks for pointing out pydb

I agree that debugger commands should also belong in the completion namespace. I'll have a look at adding that to the patch.

> The second problem I have is that completion is not all that sensitive to the preceding context.

The idea is that the namespace that is available to the completer at any time will be the same as the local and global identifiers and keywords that are available in the same scope. I think it makes sense to complete everything that is valid in the current scope because that makes for a more useful introspection tool. Thats what frame.f_locals and frame.f_globals are about (if foo and bar are available in the current scope, and you step into a function outside of that scope then foo and bar will no longer be available in the completer's namespace). I notice this is also used in pydb's complete method under certain circumstances.

I'll definitely take a closer look at pydb. I probably wouldn't have needed to write this if I'd known about it before :)