Larry Hastings added the comment:
(And hooray for that, given the meteoric rise of AtheOS. :| )
I'm going to go way out on a limb and say that Guido hasn't made a
pronouncement here. Also, the discussions cited by Martin are about entire new
platforms (AtheOS, Haiku), whereas what we're talking about here is an
additional architecture for an existing platform (m68k on linux).
So I'm going to use my best judgement. I'm willing to accept the patch for
3.5, provided that:
* it's understood that m68k is not an officially supported
platform, and
* this is sufficient, we won't need loads of other m68k support
patches. (As the saying goes, this patch should not be a
"foot in the door".)
I do have two questions:
* With this patch applied, how much of the test suite passes?
* Is there a way that the configure check could be skipped on non-m68k
platforms? Because 99.999999% of the time, that check is irrelevant,
and configure is already slow enough.
Could you possibly just drop the GCC check? Do you genuinely support
m68k on linux using revisions of GCC that don't support inline
assembly?
Finally, Mark Dickinson is right: since this patch changes behavior in an
incompatible way, it's not permissible to check it in for 3.4. Sorry.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20904>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
