<div class="gmail_quote">On Thu, Sep 2, 2010 at 09:27, Tony Cappellini <span dir="ltr"><<a href="mailto:cappy2112@gmail.com">cappy2112@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">>> If it's a known bug, why don't they pull that installer down?<br>
><br>
> Then there would be no installers for 2.6.6, effectively removing Windows<br>
> from the list of supported platforms. The compile step is nice, but not<br>
> required, and certainly not a show-stopper.<br>
<br>
</div>I guess a more important question is, Once installation completes<br>
without doing the compile step,<br>
does the same module have a problem compiling when it is imported as<br>
part of a normal script execution?<br>
</blockquote></div><br><div>Nope, everything else is fine. The bug in the installer had to do with bad command line options to compileall.py which is what goes through and executes the pyc compilation on stdlib modules. That script was failing to run properly, but compilation itself does work.</div>