This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author BreamoreBoy
Recipients BreamoreBoy, benjamin.peterson, georg.brandl, larry, mark.dickinson, pitrou, schwab, skrah, tim.peters
Date 2014-03-23.22:21:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395613310.24.0.141451504164.issue20904@psf.upfronthosting.co.za>
In-reply-to
Content
I've asked a simple question and I've *NOT* had an answer.  Antoine's response to Larry's question "Does Python still officially support m68k?" is certainly pertinent "Certainly not. We haven't had any 68k buildbot in ages (not sure we ever had any, actually)."  The more I see here, the more laughable I think the situation is.  Core devs have time to spend on an issue for an unsuppoorted platform, but don't have the time to support the 4500 issues that are presumably aimed at supported platforms.  What gives?
History
Date User Action Args
2014-03-23 22:21:50BreamoreBoysetrecipients: + BreamoreBoy, tim.peters, georg.brandl, mark.dickinson, pitrou, larry, benjamin.peterson, skrah, schwab
2014-03-23 22:21:50BreamoreBoysetmessageid: <1395613310.24.0.141451504164.issue20904@psf.upfronthosting.co.za>
2014-03-23 22:21:50BreamoreBoylinkissue20904 messages
2014-03-23 22:21:50BreamoreBoycreate