[Python-Dev] Compiling Python 3.2 on Cygwin fails (original) (raw)

Brian Curtin brian.curtin at gmail.com
Tue Jul 5 21🔞22 CEST 2011

On Tue, Jul 5, 2011 at 14:12, Dan Stromberg <drsalists at gmail.com> wrote:

On Tue, Jul 5, 2011 at 7:25 AM, David Robinow <drobinow at gmail.com> wrote:

Cygwin is not really a supported platform. ... [Ultimately somebody with an interest in cygwin will need to get active in python development. I've been meaning to do this but life gets in the way.] I was bitten by the lack of Cygwin support in 3.2 as well. IMO, python-dev needs continuous integration on a build farm that includes representative platforms. Most of the machines in the farm could be virtualboxes. 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.

We've had that for some time now: http://www.python.org/dev/buildbot/

There are several issues on the bug tracker about cygwin build issues, but to my knowledge, none of them have included successful patches. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20110705/520c851e/attachment.html>

More information about the Python-Dev mailing list