<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Jan 31, 2013 at 11:14 PM, Antoine Pitrou <span dir="ltr"><<a href="mailto:solipsis@pitrou.net" target="_blank">solipsis@pitrou.net</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">On Fri, 1 Feb 2013 11:00:24 +1000<br>
Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br>
> On Fri, Feb 1, 2013 at 9:50 AM, Antoine Pitrou <<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>> wrote:<br>
> > On Thu, 31 Jan 2013 23:52:27 +0100 (CET)<br>
> > matthias.klose <<a href="mailto:python-checkins@python.org">python-checkins@python.org</a>> wrote:<br>
> >> <a href="http://hg.python.org/cpython/rev/8ee6d96a1019" target="_blank">http://hg.python.org/cpython/rev/8ee6d96a1019</a><br>
> >> changeset: 81859:8ee6d96a1019<br>
> >> branch: 2.7<br>
> >> parent: 81855:df9f8feb7444<br>
> >> user: <a href="mailto:doko@python.org">doko@python.org</a><br>
> >> date: Thu Jan 31 23:52:03 2013 +0100<br>
> >> summary:<br>
> >> - Issue #17086: Backport the patches from the 3.3 branch to cross-build<br>
> >> the package.<br>
> ><br>
> > You aren't supposed to add new features to bugfix branches. Did you<br>
> > have a specific reason to do this?<br>
><br>
> One of the reasons for the long maintenance period on 2.7 is to keep<br>
> it building as the underlying platforms change. With the rise of ARM<br>
> systems, being able to reliably cross-build Python 2.7 for ARM from an<br>
> x86_64 system is fairly important.<br>
<br>
</div>I would like to see a better argument for this. The rise of ARM systems<br>
is the rise of ARM systems powerful enough to build Python without<br>
cross-compiling (which is why we *now* have ARM buildbots).<br>
The very small ARM systems which need cross-compiling have existed for<br>
decades.<br></blockquote><div><br></div><div style>It is quite common for developers to build a single code base on a single workstation targeting a plethora of platforms all at once. Requiring native systems with self hosting tool-chains for builds is a non-starter as those often don't exist. Making Python 2.7's configure+makefiles easier to cross compile out of the box is a good thing.</div>
<div><br></div><div style>Side note: we really need a cross compiling build-bot host + target system or we'll inevitably break this.</div><div style><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> That said, as a procedural point for build related new features in<br>
> 2.7, I agree they should be proposed, with an explicit rationale, on<br>
> python-dev before proceeding with the commit.<br>
<br>
</div>I think this huge changeset should be reverted. It's a complete failure<br>
in terms of procedure and following the rules. "Just because it can be<br>
useful" is not a good enough reason to violate our release model<br>
without even asking.<br></blockquote><div><br></div><div style>That's up to the 2.7 release manager. Yes, this could have been done better by asking first. But IMNSHO I'd prefer to see it stay in.</div><div style>
<br></div><div style>-gps</div><div style> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards<br>
<span class="HOEnZb"><font color="#888888"><br>
Antoine.<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/greg%40krypto.org" target="_blank">http://mail.python.org/mailman/options/python-dev/greg%40krypto.org</a><br>
</div></div></blockquote></div><br></div></div>