This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mhammond
Recipients cgohlke, koen, loewis, mhammond, tarek
Date 2010-04-27.23:37:13
SpamBayes Score 0.0043294914
Marked as misclassified No
Message-id <1272411435.64.0.0634093659124.issue7833@psf.upfronthosting.co.za>
In-reply-to
Content
the pywin32 DLLs have 2 heads.  They are Python extension modules as well as regular DLLs.  They are built by distutils and therefore have no manifests - I think many packages use distutils to build their extension modules - it is just that they usually don't have a .dll extension.

I fear that simply adding a manifest to those DLLs will put them in the same position we have before issue4120 was addressed, and these .dlls do need a way to be installed into System32 (or somewhere else on the global PATH) to function as COM servers etc.  I need to experiment with this.
History
Date User Action Args
2010-04-27 23:37:15mhammondsetrecipients: + mhammond, loewis, koen, tarek, cgohlke
2010-04-27 23:37:15mhammondsetmessageid: <1272411435.64.0.0634093659124.issue7833@psf.upfronthosting.co.za>
2010-04-27 23:37:13mhammondlinkissue7833 messages
2010-04-27 23:37:13mhammondcreate