[issue11097] MSI: Remove win32com dependency from installer generator

2015-03-03 Thread Steve Dower
Changes by Steve Dower : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue11097] MSI: Remove win32com dependency from installer generator

2015-03-03 Thread Mark Lawrence
Mark Lawrence added the comment: This can now be closed as out of date. -- components: +Windows nosy: +steve.dower, tim.golden, zach.ware ___ Python tracker ___ _

[issue11097] MSI: Remove win32com dependency from installer generator

2014-06-18 Thread Martin v . Löwis
Martin v. Löwis added the comment: There is a high chance that 3.5 might use an entirely different MSI generator, possibly based on WiX. If that happens, this issue will be outdated. -- ___ Python tracker

[issue11097] MSI: Remove win32com dependency from installer generator

2014-06-16 Thread Mark Lawrence
Mark Lawrence added the comment: If this report is (still) true I'd assume that we'd want to eventually action it. Otherwise can we close this as out of date? -- nosy: +BreamoreBoy type: -> enhancement versions: +Python 3.5 -Python 2.7, Python 3.1, Python 3.2, Python 3.3

[issue11097] MSI: Remove win32com dependency from installer generator

2011-02-02 Thread anatoly techtonik
New submission from anatoly techtonik : The MSI installer is generated using msilib.py from http://svn.python.org/projects/python/branches/release27-maint/Tools/msi that is dependent from external win32com module. We also have internal 'msilib' module that is unused for some reason. Is it pos