<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 3, 2010, at 11:26 AM, Alexander Belopolsky wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">This may not be a problem for smart tools, but for me and a simple<br>editor what used to be:<br></span></span></blockquote></div><div><br></div><div>Maybe this is the real problem? It's 2010, we should all be far enough beyond EDLIN that our editors can jump to the definition of a Python class. Even Vim can be convinced to do this (<<a href="http://rope.sourceforge.net/ropevim.html">http://rope.sourceforge.net/ropevim.html</a>>). Could Python itself make this easier? Maybe ship with a command that says "hey, somewhere on sys.path, there is a class with <this name>. Please run '$EDITOR file +line' (or the current OS's equivalent) so I can look at the source code".</div><div><br></div><div><br></div></body></html>