Raymond Hettinger: "Is there any downside to keeping this code?"

I don't think that we have much code specific to Tiger, except maybe some skips in unit tests. Maybe we can just remove the buildbot but don't touch the code.

My issue is more that I would like to see green buildbots. I don't see the purpose of having a buildbot if it's known to be broken. It's a pain to recall which buildbots are known to be broken or not.


> That's not true.  The one failing test, test_uuid, was just added last month.  Note that the 3.5 Tiger buildbot has not test failures.

Ah? I didn't know. Maybe my issue was more that Tiger fails randomly. In fact, I don't recall exactly why I wanted to drop Tiger support :-)


> But, more importantly, at the moment, the 10.4 Tiger buildbot is the *only* working Mac buildbot we have.

Oh wow, I didn't know. Travis CI provides Linux containers, AppVeyor provides Windows VMs. Is there a similar free service for macOS? Or maybe not free for everyone, but free for the Python CI?


> Here's where the Tiger 3.x buildbot started failing: (...)

I created the issue #29925 for test_uuid failure.


> Until we have other working OS X buildbots, the Tiger one should remain.  It is serving a useful purpose.

My general view on buildbots is that one buildbot needs a maintainer or should go away.

Yeah, I have to long term plan to remove most buildbots :-D For example, the situation didn't evolved for the OpenIndiana buildbot...