<!--/*SC*/DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"/*EC*/-->
<html><head><title></title><style type="text/css"><!--body{padding:1ex;margin:0px;font-family:sans-serif;font-size:small;}a[href]{color:-moz-hyperlinktext !important;text-decoration:-moz-anchor-decoration;}blockquote{margin:0;border-left:2px solid #144fae;padding-left:1em;}blockquote blockquote{border-color:#006312;}blockquote blockquote blockquote{border-color:#540000;}--></style></head><body><div style="font-family: Arial; font-size: medium;" dir="ltr"><div class="defangedMessage">
<div id="me38540">
<div>Tom,</div>
<div> </div>
<div>> You don't need to add a whole load of imports inside a "if False" block to make py2exe add them. If I recall correctly there is a option in py2exe to force exclude and include modules when compiling.</div>
<div> </div>
<div><embarrased grin> DOH! You're right! </embarrassed grin></div>
<div> </div>
<div>I've been doing a lot of work with our automated build cycle and I must have looked at 100 different setup.py's. We do use these features to fine tune our py2exe setup scripts for each application. We just missed using these features for forcing our large 'standard library (kitchen sink)' collection of modules.</div>
<div> </div>
<div>Good catch!</div>
<div> </div>
<div>Thank you,</div>
<div>Malcolm</div>
</div>
</div></div></body></html>