<div class="gmail_quote">On Tue, Jul 5, 2011 at 14:12, Dan Stromberg <span dir="ltr"><<a href="mailto:drsalists@gmail.com">drsalists@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><div class="gmail_quote">On Tue, Jul 5, 2011 at 7:25 AM, David Robinow <span dir="ltr"><<a href="mailto:drobinow@gmail.com" target="_blank">drobinow@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div><div>
<br>
</div></div> Cygwin is not really a supported platform. </blockquote><div>... <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">[Ultimately somebody with an<br>
interest in cygwin will need to get active in python development. I've<br>
been meaning to do this but life gets in the way.]<font color="#888888"><br></font></blockquote><div><br>I was bitten by the lack of Cygwin support in 3.2 as well.<br><br>IMO, <span>python-dev needs continuous integration on a build farm that includes representative platforms. Most of the machines in the farm could be virtualboxes.<br>
<br>I don't think the problem is so much that the right people haven't gotten involved, as that the currently-involved people don't know when they're breaking something for someone else due to the lack of continuous integration.</span></div>
</div></blockquote><div><br></div><div>We've had that for some time now: <a href="http://www.python.org/dev/buildbot/">http://www.python.org/dev/buildbot/</a></div><div><br></div><div>There are several issues on the bug tracker about cygwin build issues, but to my knowledge, none of them have included successful patches.</div>
</div>