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 janssen
Recipients eric.araujo, janssen, loewis, ronaldoussoren
Date 2010-06-23.18:03:07
SpamBayes Score 0.0069264877
Marked as misclassified No
Message-id <1277316188.56.0.592798281077.issue9048@psf.upfronthosting.co.za>
In-reply-to
Content
Bit of a chicken/egg issue here.  Since we haven't had OS X buildbots for very long, and the ones we do have represent odd configurations, I think it's premature to say that "the port *doesn't* pass the test suite on
a regular manner".  I think it's just as reasonable to say that the developers making changes just aren't aware of bad side-effects on OS X.  A good way to remedy that would be to make those bad side-effects more apparent, for example by adding an OS X buildbot into the "stable" set.

Another issue is that none of the three OS X buildbots now running are really good representatives of the technology that most people I know who use OS X really use.  That would be an Intel Core 2 Duo machine running Snow Leopard.
History
Date User Action Args
2010-06-23 18:03:08janssensetrecipients: + janssen, loewis, ronaldoussoren, eric.araujo
2010-06-23 18:03:08janssensetmessageid: <1277316188.56.0.592798281077.issue9048@psf.upfronthosting.co.za>
2010-06-23 18:03:07janssenlinkissue9048 messages
2010-06-23 18:03:07janssencreate