Pythonwin is terrible!

[david_ullrich at my-deja.com]

In article <3940af8b.236270458 at news.online.no>,
  thomas at cintra.no (Thomas Weholt) wrote:
> Yo,
>
> PythonWin has some great stuff, like "partial" code-completion. I too
> have som problems with code gone haywire, sometimes Pythonwin gets
> stuck, but most of the time it`s a good alternative to IDLE.
>
> I use Emacs under Linux and it works just fine. Just wish the
> code-completion-thingy in Pythonwin could somehow be implemented in
> Emacs. That`s probably never gonna happen, but an editor with these
> capabilities would help the python grow bigger, and Windows-converts
> like myself get over the habits gotten from programming in
> Delphi/JBuilder. Code-completion, Code-Insight, parameter-lookups ...
> It would be nice wouldn`t it??!

    Surely this sort of thing is much harder in Python due
to the extremely dynamic nature of the language? At least
parameter lookups seem much trickier, in fact it seems
impossible to do that perfectly in Python: In Delphi the
compiler knows exactly what function a given identifier is
referring to at a given place in the code - otoh in Python
you can do something like

def F(n): return n

def G(n,m): return n + m

F = G

Now when you type 'F(' the parameter-lookup thingie should
prompt you for _two_ parameters, in spite of the "declaration"
of F as a function that takes one parameter.

    The code that maps "F" to G could be anywhere - I don't
see how a perfect parameter-lookup is possible.

DU

> Ah well ...
>
> Thomas
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.