On Nov 3, 2010, at 11:26 AM, Alexander Belopolsky wrote: > This may not be a problem for smart tools, but for me and a simple > editor what used to be: 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 (<http://rope.sourceforge.net/ropevim.html>). 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". -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20101103/9d3937da/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4