REPOST: Re: COM Registration Attributes

Alex Martelli aleax at
Fri Dec 28 16:02:44 CET 2001

"Bill Bell" <bill-bell at> wrote in message
news:5edaf477.0112280645.246f7229 at
> I have been wondering again about the best way of handling a
> collection of Windows registry key additions, deletions or changes as
> part of registering a Python COM server.
> 4. Wrap atl.dll and make it part of the standard Windows distribution.
> changes the specs for .rgs scripts. (Mind you, isn't this stuff meant
> to become less of an issue?) Option 4 looks nicest to me.

Maybe not to Microsoft's legal department, though.  It would be at
least wise to check with them rather than assuming they'd be glad to
see some of their "redistributables" redistributed this way (i.e., as
a part of a development environment).

> What do others think?

Wrapping _winreg (or the win32all equivalent thereof) seems the
most clever option to me.  Such a wrapper might be part of some
Python distribution (or more sensibly of win32all).


========= WAS CANCELLED BY =======:
From: "Alex Martelli" <aleax at>
Newsgroups: comp.lang.python
Subject: cmsg cancel <a0i1ih$4sf$1 at>
Control: cancel <a0i1ih$4sf$1 at>
Date: Mon, 31 Dec 2001 03:35:33 GMT
Organization: A poorly-installed InterNetNews site
Lines: 2
Message-ID: <cancel.a0i1ih$4sf$1 at>
X-Trace: 1009775342 27193 (31 Dec 2001 05:09:02 GMT)
X-Complaints-To: usenet at
NNTP-Posting-Date: Mon, 31 Dec 2001 05:09:02 +0000 (UTC)
X-No-Archive: yes
X-Unac4ncel: yes
X-Commentary: I love NewsAgent 1.10 and the Sandblaster Cancel Engine Build 74 (19 March 1999)

This message was cancelled from within Mozilla.

More information about the Python-list mailing list