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 vstinner
Recipients BTaskaya, Yonatan Goldschmidt, abarbu, alanc, brett3, cgrzemba, gaige, giampaolo.rodola, gwr, ijdt.editor, jcea, jclulow, jgardner100, jm650, jomasoftmarcel, jorge.schrauwen, jstasiak, kulikjak, marcheschi, mariuspana, michael.laspina, mimi.vx, olafbohlen, omnios, otis, pablogsal, pfirmsto, predrag.zecevic.1961, rhettinger, robertdfrench, siepkes, tbalbers, terry.reedy,, vstinner, wiedi, yanchii
Date 2020-11-06.16:32:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Copy of my email sent to python-dev.

Since I created the issue and the PR, and sent this email to
python-dev (one week ago), many Solaris and Solaris-like (ex: Illumos)
users replied that the operating system is definitively alive. I
didn't know that Oracle still ships new Solaris updates every month:
that's a good thing!

But this is not enough to support a platform. We would need proactive
contributors to fix known Solaris issues, but also fix new Solaris
issues (either regressions, or bugs newly discovered). We would also
need a buildbot to run the Python test suite on Solaris (or again, a
Solaris-like OS).

The good news is that Jakub Kulik started to fix some Solaris issues.
I understood that Solaris and Solaris-like operating systems do have
downstream patches on Python to fix a bunch of bugs. It seems like
some people want to push these fixes to Python upstream which is also
a good sign.

The other problem that I wanted to discuss is that fixing Solaris
issues require core devs (who merge PRs) accessing Solaris. If
contributors send patches and some core devs are fine with merging
fixes without being able to test them manually, I'm also fine with

My first intent was to remove support for a definitely dead operating
system, but it seems like I was completely wrong (it's alive!). Thanks
to people starting to fix Solaris issues, I close my PR and I no
longer plan to drop Solaris support. I prefer to leave bpo-42173 open
for now, since people decide to use it as a place to collaborate on
fixing Solaris issues.

Once most tests will pass on the master branch, I also hope that
someone will set up a buildbot *and* fix issues discovered by this
buildbot. Sorry but just setting up a buildbot doesn't solve any
problem, it only increases the maintenance burden for people who
maintain the buildbot fleet. For example, we have two AIX buildbots, I
report bugs on, but it seems like nobody is available
to fix them...

Overall, I'm quite happy with what is happening with Solaris! More
collaboration, issues being fixed in Python upstream. I just hope that
this work will continue next months. ;-)
Date User Action Args
2020-11-06 16:32:11vstinnersetrecipients: + vstinner, rhettinger, terry.reedy, jcea, giampaolo.rodola, jstasiak, pablogsal, BTaskaya, kulikjak,, gaige, Yonatan Goldschmidt, wiedi, mimi.vx, jclulow, omnios, pfirmsto, alanc, brett3, robertdfrench, jm650, tbalbers, mariuspana, siepkes, cgrzemba, marcheschi, abarbu, predrag.zecevic.1961, jorge.schrauwen, olafbohlen, otis, yanchii, michael.laspina, ijdt.editor, jomasoftmarcel, jgardner100, gwr
2020-11-06 16:32:11vstinnersetmessageid: <>
2020-11-06 16:32:11vstinnerlinkissue42173 messages
2020-11-06 16:32:11vstinnercreate