Comments on: Any version bdist_msi for pure Python packages http://ramblings.timgolden.me.uk/2009/05/05/any-version-bdist_msi-for-pure-python-packages/ The ramblings of Tim Golden Fri, 10 Feb 2012 06:27:43 +0000 http://wordpress.org/?v=2.2 By: tim http://ramblings.timgolden.me.uk/2009/05/05/any-version-bdist_msi-for-pure-python-packages/#comment-981 tim Wed, 06 May 2009 07:13:23 +0000 http://ramblings.timgolden.me.uk/2009/05/05/any-version-bdist_msi-for-pure-python-packages/#comment-981 @Brad: well, my memory obviously played me false -- I thought I remembered that the MSI was previously tied to one version. Obviously not. Still, as you say, it's always good to see some ownership and maintenance in the stdlib, and especially on the Windows side. The issue comments do point out that, with whatever changes have taken place under the covers, it should now be possible to add a "Change" button visible in "Add & Remove Progs" which would allow you to install all your existing modules for a new version of Python. As to your building a joint MSI, I'm afraid I'm pretty much ignorant. Have you tried posting the question to the lists? Be interesting to see if someone had already solved the problem. @Brad: well, my memory obviously played me false — I thought I remembered that the MSI was previously tied to one version. Obviously not. Still, as you say, it’s always good to see some ownership and maintenance in the stdlib, and especially on the Windows side. The issue comments do point out that, with whatever changes have taken place under the covers, it should now be possible to add a “Change” button visible in “Add & Remove Progs” which would allow you to install all your existing modules for a new version of Python.

As to your building a joint MSI, I’m afraid I’m pretty much ignorant. Have you tried posting the question to the lists? Be interesting to see if someone had already solved the problem.

]]> By: Brad Allen http://ramblings.timgolden.me.uk/2009/05/05/any-version-bdist_msi-for-pure-python-packages/#comment-980 Brad Allen Wed, 06 May 2009 01:18:23 +0000 http://ramblings.timgolden.me.uk/2009/05/05/any-version-bdist_msi-for-pure-python-packages/#comment-980 Great! I've been using bdist_msi to distribute packages to customers who use Windows, so I'm glad it's being maintained with new features being added. However, I've had no problem installing to arbitrary Python locations (such as virtualenv directories), so I don't understand the benefit of the new feature. btw, any idea how to build an MSI installer containing multiple different eggs (each with its own setup.py)? Currently I am building MSI installers for all the third party libraries along with my own app, so my customer is getting a handful of different installers. It would be nice if I could build one big installer. Great! I’ve been using bdist_msi to distribute packages to customers who use Windows, so I’m glad it’s being maintained with new features being added.

However, I’ve had no problem installing to arbitrary Python locations (such as virtualenv directories), so I don’t understand the benefit of the new feature.

btw, any idea how to build an MSI installer containing multiple different eggs (each with its own setup.py)? Currently I am building MSI installers for all the third party libraries along with my own app, so my customer is getting a handful of different installers. It would be nice if I could build one big installer.

]]>