[Tutor] How do I use calldll and windll?

spi bleh99@hotmail.com
Thu, 29 Mar 2001 19:22:14 -0500


I figured out this issue, thought that I would post the solution in
case anyone else had this problem

I was importing the modules in the wrong order

i was doing

>>> import windll
>>> import calldll

The right way to do it is

>>> import calldll
>>> import windll

----- Original Message -----
From: "D-Man" <dsh8290@rit.edu>
To: <tutor@python.org>
Sent: Thursday, March 29, 2001 11:43 AM
Subject: Re: [Tutor] How do I use calldll and windll?


> On Thu, Mar 29, 2001 at 11:21:53AM -0500, spi wrote:
> | Here are the results I get, I don't understand why it's not showing the
> | other modules
> |
> | >>> import windll
> | >>> print windll
> | <module 'windll' from 'd:\python20\lib\dynwin\windll.pyc'>
> | >>> dir( windll )
> | ['__builtins__', '__doc__', '__file__', '__name__']
> | >>>
>
> Ok, so it found the module in the directory you expected, but it came
> from the .pyc, not .py file.  (.pyc's are simply bytecode versions of
> .py files)  Also, the module doesn't contain anything except for it's
> name and docstring.  You could try printing the docstring to see what
> (if anything) it says.
>
> I would recommend deleting the .pyc file so that the interpreter has
> to parse and re-bytecompile the .py file again.  Perhaps you somehow
> ended up with an outdated or lacking .pyc file?
>
> HTH,
> -D
>
>
> PS.  the previous message from "spi" was really a 'bounce' from my (see
mutt's
>      docs for a definition of the (overloaded) term) personal box.  I
>      hadn't noticed (in my hasty reading) the long code included,
>      sorry for sending all such a long message
>
> _______________________________________________
> Tutor maillist  -  Tutor@python.org
> http://mail.python.org/mailman/listinfo/tutor