Python packaging (particularly on Windows) is a definite pain point. That "no module named zope interface" is apparently due to the base Zope module not having

Python packaging (particularly on Windows) is a definite pain point. That "no module named zope interface" is apparently due to the base Zope module not having an __init__.py. Every single time I install I have to manually add that file. One of the golang attractions is the ability to quickly build a single-file distributable. The tradeoff is reduced programmer productivity. In terms of 'make it work then optimize later,' my latest approach has been to use eGenix PyRun (http://www.egenix.com/products/python/PyRun/ http://www.egenix.com/products/python/PyRun/). For final distribution, compile then remove all the .py files in the tree (leaving just the compiled Python and binary dll/libraries) and create an alias link to the executable. Not perfect, but saves hours of time building distributions.