I personally agree that huge changesets aren't good. But I can also see
the problem of cross compiling should be sooner or later addressed.
I'm fairly interested in cross building python on android too.
A point to support cross compiling (instead native build arm-on-arm)
could be android doesn't provide (to my knowledge) a native toolchain:
that's a quite large target.
And assuming arm equals unix so there's always an installed or
installable compiler on it is not always the case.
If I can suggest a simple solution that'd be a simple makefile to
compile python (I have one on my own): no "configure" magic involved
more akin to the windows build style (yes, I've just said the W* word).
I hope this helps,
antonio
- Issue #17086: Backport the patches from the 3.3 branch to cross-build
the package.
You aren't supposed to add new features to bugfix branches. Did you
have a specific reason to do this?
One of the reasons for the long maintenance period on 2.7 is to keep
it building as the underlying platforms change. With the rise of ARM
systems, being able to reliably cross-build Python 2.7 for ARM from an
x86_64 system is fairly important.
I would like to see a better argument for this. The rise of ARM systems
is the rise of ARM systems powerful enough to build Python without
cross-compiling (which is why we *now* have ARM buildbots).
The very small ARM systems which need cross-compiling have existed for
decades.
That said, as a procedural point for build related new features in
2.7, I agree they should be proposed, with an explicit rationale, on
python-dev before proceeding with the commit.
I think this huge changeset should be reverted. It's a complete failure
in terms of procedure and following the rules. "Just because it can be
useful" is not a good enough reason to violate our release model
without even asking.
Regards
Antoine.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/a.cavallo%40cavallinux.eu
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
