Regarding having a Solaris buildbot: if someone provides a Solaris buildbot then the deal is that that someone or some other party must look after that buildbot and fix problems that appear in it in a timely manner. Broken buildbots stop releases and I don't want to be in a situation in which I need to halt a release because the Solaris buildbot is broken and there is no-one to fix it in time.

In the past, we had to dealt with similar situations and not only is stressful but normally ends in me or Victor having to login in a buildbot for a platform that we are not experts on to try to fix it in time.

On Fri, 30 Oct 2020, 09:29 Ronald Oussoren via Python-Dev, <> wrote:

> On 29 Oct 2020, at 22:43, Victor Stinner <> wrote:
> Hi,
> I propose to drop the Solaris support in Python to reduce the Python
> maintenance burden:
> I wrote a draft PR to show how much code could be removed (around 700
> lines in 65 files):

A significant fraction of that is in comments and documentation. A number of the changes in documentation would be good to go in regardless of the resolution of this proposal.

> In 2016, I asked if we still wanted to maintain the Solaris support in
> Python, because Solaris buildbots were failing for longer than 6
> months and nobody was able to fix them. It was requested to find a
> core developer volunteer to fix Solaris issues and to set up a Solaris
> buildbot.
> Four years later, nothing has happened. Moreover, in 2018, Oracle laid
> off the Solaris development engineering staff. There are around 25
> open Python bugs specific to Solaris.

As another data point: There is someone on BPO that files issues about Solaris on BPO, including PRs. It might be worthwhile to ask that person if they can provide a buildbot (while making clear that this results in the assumption that they’d look after Solaris port).

If Solaris would get dropped I’d prefer option 2


Twitter / @ronaldoussoren

Python-Dev mailing list --
To unsubscribe send an email to
Message archived at
Code of Conduct: