Greetings!
How wise is it to base code on inspect? Specifically on things like
live frames on the stack and whatnot. It occurs to me that this is
leaning towards implementation details, and away from pure, pristine Python.
As an example, I have this routine in a module I'm working on:
def
On Wed, 11 Nov 2009 18:15:22 -0800, Ethan Furman wrote:
Greetings!
How wise is it to base code on inspect? Specifically on things like
live frames on the stack and whatnot. It occurs to me that this is
leaning towards implementation details, and away from pure, pristine
Python.
As an
On Sep 28, 9:57 pm, Chris Pax [EMAIL PROTECTED] wrote:
Hello,
I recently been trying to use the inspect module to inspect the
arguments of gtk objects, such as gtk.Button. I tried like this:
inspect.getargspec(gtk.Button.__init__)
and get the fallowing error:
File stdin, line 1, in
I recently been trying to use the inspect module
to inspect the arguments of gtk objects, such as gtk.Button.
does anybody have any idea?
Chris
You might try the following newsgroup on the Gmane server
for Python / Gtk questions
gmane.comp.gnome.gtk+.python
On 9/29/07, Chris Pax [EMAIL PROTECTED] wrote:
Hello,
I recently been trying to use the inspect module to inspect the
arguments of gtk objects, such as gtk.Button. I tried like this:
inspect.getargspec(gtk.Button.__init__)
and get the fallowing error:
File stdin, line 1, in module
On Oct 1, 12:53 pm, BJörn Lindqvist [EMAIL PROTECTED] wrote:
On 9/29/07, Chris Pax [EMAIL PROTECTED] wrote:
Hello,
I recently been trying to use the inspect module to inspect the
arguments of gtk objects, such as gtk.Button. I tried like this:
inspect.getargspec(gtk.Button.__init__)
Hello,
I recently been trying to use the inspect module to inspect the
arguments of gtk objects, such as gtk.Button. I tried like this:
inspect.getargspec(gtk.Button.__init__)
and get the fallowing error:
File stdin, line 1, in module
File /usr/lib/python2.5/inspect.py, line 743, in
I'm trying to learn about introspection in Python. my ultimate goal
is to be able to build a module text database of all modules that
are in the sys.path, by discovering all candidate modules (I've
already done that), importing all of them, and then introspecting on
each module to discover its
Benjamin Rutt wrote:
I'm trying to learn about introspection in Python. my ultimate goal
is to be able to build a module text database of all modules that
are in the sys.path, by discovering all candidate modules (I've
already done that), importing all of them, and then introspecting on
Fernando Perez [EMAIL PROTECTED] writes:
I certainly don't want to discourage you from learning about python
introspection, it's one of the most fun aspects of the language. But just as
an FYI, the pydoc system already does much of what you have in mind, at least
if I'm reading your
Benjamin Rutt wrote:
Fernando Perez [EMAIL PROTECTED] writes:
I certainly don't want to discourage you from learning about python
introspection, it's one of the most fun aspects of the language. But just
as an FYI, the pydoc system already does much of what you have in mind, at
least if
Benjamin Rutt [EMAIL PROTECTED] writes:
what I am actually trying to do is to build a database of Python
modules. so then later, I can write a tool in my favorite editor
(Emacs) to invoke some forms of completion against this database
(e.g. os.removTAB or socket.TAB to see a list of all
12 matches
Mail list logo
