On Fri, 5 Mar 2010 06:36:50 -0800 (PST)
tfer <[email protected]> wrote:
> Cool, I got to play with this a little last night. It seemed to choke
> on a "load recursive" done at the top level of the ipython
> ditribution, but perhaps I got impatient, nothing seemed to be
> happening after a couple of minutes so I killed the session.
find Package/ipython/ -iname \*.py | wc -l
953
So 953 files to pull docstrings from. I'll see if g.es() updates are shown
during a busy loop, but maybe not.
> Worked
> fine when I tried it on a lower levels.
>
> I can see this helping "code groking" a lot, you can explore the
> modules, their file organization, their docstrings, (which you can add
> to as your understanding grows)
Just to clarify the docstrings aren't written back, if you want to modify the
real docstring just double-click load the file first.
> Rather than keep pestering you with feature requests, I was wondering
> about the possibility of adding a
[end of email] :-)
Hmm, I started the recursive import for ipython, and it's still not done... I
guess I'll let it keep going. I suppose some modules may be more demanding for
ast scanning than others. Just seems simpler to use ast.get_docstring() than
any skip the comments kind of text reading. Because strictly speaking:
"This is " 'one docstring'
("And this"
''' is another)
[time passes]
...still going, I wonder if ast is repeatedly importing a large number of
things referenced from each module it's scanning...
...later... meh, been gone so long now it might as well be considered crashed.
I'll see where it's actually hanging up.
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
