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 db3l
Recipients db3l, gregory.p.smith, martin.panter, ned.deily
Date 2016-09-09.22:19:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473459570.94.0.369945177398.issue28039@psf.upfronthosting.co.za>
In-reply-to
Content
It's been on the cusp of shutdown a few times now, but tweaks to maintain compatibility for the occasional issue always seem to materialize (thanks to Ned in many cases).

To Ned's question, the slave is currently operating under 2.5.1 which I must have set up since Tiger originally came with 2.3.  I'm sure I could bump that to 2.6+ to avoid the error if there's still value.  It would probably be less work if the installer script could still use 2.5.1 if only because I'm not sure of what other dependencies it uses I might need to fix along with Python.

Gregory, while the slave's value purely as a test platform is probably close to non-existent at this point, another contributor to its longevity is that it still builds daily DMG installers (the bolen-dmg build slave).  So that had remained useful beyond plain testing.  I'm not positive if it's still true, but for OSX it used to be better to use the oldest build platform you could as Apple wasn't very good about backwards compatibility of builds on newer versions.  And originally Tiger was the only free machine I had.

With that said, it's not clear anyone still references the daily DMGs any more, or gets much benefit from them.  So I'm not wedded to keeping this operating, if instead it's finally reached the time for retirement.

-- David
History
Date User Action Args
2016-09-09 22:19:30db3lsetrecipients: + db3l, gregory.p.smith, ned.deily, martin.panter
2016-09-09 22:19:30db3lsetmessageid: <1473459570.94.0.369945177398.issue28039@psf.upfronthosting.co.za>
2016-09-09 22:19:30db3llinkissue28039 messages
2016-09-09 22:19:30db3lcreate