[python-win32] COM Server won't go away!

[Noah Spurrier]

I created a server and registered it OK. I called it from a VisualBasic client. OK. It worked.
Then I unregistered it. Tested VB client again and it failed to find the server. OK. That was expected.

Next I modified the source of the Python server and saved it and registered it.
When I tested it from VB again it was running the OLD version. 

I thought maybe it was running from an old .pyc file, but I could not find any .pyc files around.
So then I changed the GUID (_reg_clsid_). I test again and it still runs the old copy.
So then I changed the GUID and I changed ProgramID and I have the VB client create the object with the new name.
It STILL runs the old copy!

Finally, I rename the Python source filename for the server source.
This time the VB Client FINALLY runs the new version.

So the question is, where was VB finding this crusty old copy of the server?
Was it cached in memory somehow? And why would it be tied to the Python source file name?

Is this a common problem? I couldn't find any references to this in a FAQ in the mailing list archives.

Yours,
Noah