Mark Mc Mahon <mtnbikingm...@gmail.com> added the comment: I wasn't so happy trawling through \windows\installer either :)
Creating an MSI to test is very simple, and actually quicker than I had originally thought. The latest patch (support_dir_for_msi_objs.patch) creates the one and just uses that. Optionally I could create a new one each time setUp()/tearDown(). But was thinking - let's do that if/when we need to :) The latest patch updates the tests - but no change to the C code. (I doubt the error you received is a bug in msilib, and I couldn't repro even by opening EVERY MSI in my windows\installer dir. It could be a rights/security issue? The previous test was not opening as READ ONLY - even though it never saved the db, so that may be another reason?) ---------- Added file: http://bugs.python.org/file22043/support_dir_for_msi_objs.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11702> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
