Help on help()

2008-02-21 Thread dbr517
Is there any technique for preventing help from recursing into the module tree?? If I do: import my_module help(my_module) I'd like to see ONLY help on my_module, NOT help on all the functions inherited from the various parent classes . . . A quick search of the documentation didn't turn up any

Re: Extending the import mechanism - what is recommended?

2008-02-04 Thread dbr517
On Jan 29, 2:36 pm, Steve Holden <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > I need to extend the import mechanism to support another file type. > > I've already written the necessary C library to read the file and > > return a python code object. > > > I found one example which just

Extending the import mechanism - what is recommended?

2008-01-29 Thread dbr517
I need to extend the import mechanism to support another file type. I've already written the necessary C library to read the file and return a python code object. I found one example which just sub-classed imputil.ImportManager like this: from myLib import pye_code as pye_code class MyImporter(im

documentation for tk.call interface

2007-10-16 Thread dbr517
I'm using Python + Tkinter for a small gui . . . there are LOTS of places inside Tkinter with code like this: self.tk.call('tkwait', 'variable', name) (this particular one is from the IntVar class). I've searched the Tkinter docs with no success; can someone point me at the documentation