Hi, My question is simple: do we officially support Solaris and/or OpenIndiana? Jesus Cea runs an OpenIndiana buildbot slave: http://buildbot.python.org/all/buildslaves/cea-indiana-x86 "Open Indiana 32 bits" The platform module of Python says "Solaris-2.11", I don't know the exact OpenIndiana version. A lot of unit tests fail on this buildbot with MemoryError. I guess that it's related to Solaris which doesn't allow overcommit (allocating more memory than available memory on the system), or more simply because the slave has not enough memory. There is now an issue which seems specific to OpenIndiana: http://bugs.python.org/issue27847 It might impact Solaris as well, but the Solaris buildbot is offline since "684 builds". Five years ago, I reported a bug because the curses module of Python 3 doesn't build on Solaris nor OpenIndiana anymore. It seems like the bug was not fixed, and the issue is still open: http://bugs.python.org/issue13552 So my question is if we officially support Solaris and/or OpenIndiana. If yes, how can we fix issues when we only have buildbot slave which has memory errors, and no SSH access to this server? Solaris doesn't seem to be officially supported in Python, so I suggest to drop the OpenIndiana buildbot (which is failing since at least 2 years) and close all Solaris issues as "WONTFIX". Victor
From the illumos developer’s guide: “illumos is a consolidation of software that forms the core of an Operating System. It includes the kernel, device drivers, core system libraries, and utilities. It is
What on earth is OpenIndiana? Its website is a mystery of buzzwords and PR vagueness: "openindiana Community-driven Illumos Distribution" "What is illumos ? the home of many technologies include ZFS, DTrace, Zones, ctf, [...]" "The “Hipster” branch Hipster is a codename for rapidly moving development branch of OpenIndiana and users might experience occasional breakages or problems. Hipster is using rolling-release model and only publishes installation ISOs once in a while. Every ISO release will be announced via mailing list and ..." That didn't exactly answer my questions. Clearly they don't care about anyone who isn't already a user of openindiana or illumos. So I propose that we shouldn't care about them either. On Fri, Sep 23, 2016 at 1:33 AM, Victor Stinner <victor.stinner@gmail.com> wrote:
Hi,
My question is simple: do we officially support Solaris and/or OpenIndiana?
Jesus Cea runs an OpenIndiana buildbot slave: http://buildbot.python.org/all/buildslaves/cea-indiana-x86 "Open Indiana 32 bits"
The platform module of Python says "Solaris-2.11", I don't know the exact OpenIndiana version.
A lot of unit tests fail on this buildbot with MemoryError. I guess that it's related to Solaris which doesn't allow overcommit (allocating more memory than available memory on the system), or more simply because the slave has not enough memory.
There is now an issue which seems specific to OpenIndiana: http://bugs.python.org/issue27847
It might impact Solaris as well, but the Solaris buildbot is offline since "684 builds".
Five years ago, I reported a bug because the curses module of Python 3 doesn't build on Solaris nor OpenIndiana anymore. It seems like the bug was not fixed, and the issue is still open: http://bugs.python.org/issue13552
So my question is if we officially support Solaris and/or OpenIndiana. If yes, how can we fix issues when we only have buildbot slave which has memory errors, and no SSH access to this server?
Solaris doesn't seem to be officially supported in Python, so I suggest to drop the OpenIndiana buildbot (which is failing since at least 2 years) and close all Solaris issues as "WONTFIX".
Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido)
Illumos, OpenIndiana et al are open source forks of Solaris. Back before the acquisition by Oracle, Sun open sourced the Solaris OS, called it OpenSolaris and encouraged projects to use it as an OS for x86 and other architectures. But after the acquisition, the OpenSolaris project seemed to end (I don’t know specifics) but several organizations carried on with distributions / forks of OpenSolaris. On 9/23/16, 10:49 AM, "Python-Dev on behalf of Guido van Rossum" <python-dev-bounces+david.c.stewart=intel.com@python.org on behalf of guido@python.org> wrote: What on earth is OpenIndiana? Its website is a mystery of buzzwords and PR vagueness: "openindiana Community-driven Illumos Distribution" "What is illumos ? From the illumos developer’s guide: “illumos is a consolidation of software that forms the core of an Operating System. It includes the kernel, device drivers, core system libraries, and utilities. It is the home of many technologies include ZFS, DTrace, Zones, ctf, [...]" "The “Hipster” branch Hipster is a codename for rapidly moving development branch of OpenIndiana and users might experience occasional breakages or problems. Hipster is using rolling-release model and only publishes installation ISOs once in a while. Every ISO release will be announced via mailing list and ..." That didn't exactly answer my questions. Clearly they don't care about anyone who isn't already a user of openindiana or illumos. So I propose that we shouldn't care about them either. On Fri, Sep 23, 2016 at 1:33 AM, Victor Stinner <victor.stinner@gmail.com> wrote: > Hi, > > My question is simple: do we officially support Solaris and/or OpenIndiana? > > Jesus Cea runs an OpenIndiana buildbot slave: > http://buildbot.python.org/all/buildslaves/cea-indiana-x86 > "Open Indiana 32 bits" > > The platform module of Python says "Solaris-2.11", I don't know the > exact OpenIndiana version. > > A lot of unit tests fail on this buildbot with MemoryError. I guess > that it's related to Solaris which doesn't allow overcommit > (allocating more memory than available memory on the system), or more > simply because the slave has not enough memory. > > There is now an issue which seems specific to OpenIndiana: > http://bugs.python.org/issue27847 > > It might impact Solaris as well, but the Solaris buildbot is offline > since "684 builds". > > Five years ago, I reported a bug because the curses module of Python 3 > doesn't build on Solaris nor OpenIndiana anymore. It seems like the > bug was not fixed, and the issue is still open: > http://bugs.python.org/issue13552 > > So my question is if we officially support Solaris and/or OpenIndiana. > If yes, how can we fix issues when we only have buildbot slave which > has memory errors, and no SSH access to this server? > > Solaris doesn't seem to be officially supported in Python, so I > suggest to drop the OpenIndiana buildbot (which is failing since at > least 2 years) and close all Solaris issues as "WONTFIX". > > Victor > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/david.c.stewart%40intel.c...
My guess is that Oracle owns the brand "Solaris" and its awful lawyers have done this. I don't think it's worth our time to support either Solaris or its descendants unless Oracle pays for it. It's too bad for the open source participants in OpenIndiana but realistically we just can't afford the distraction. On Fri, Sep 23, 2016 at 10:55 AM, Stewart, David C <david.c.stewart@intel.com> wrote:
Illumos, OpenIndiana et al are open source forks of Solaris. Back before the acquisition by Oracle, Sun open sourced the Solaris OS, called it OpenSolaris and encouraged projects to use it as an OS for x86 and other architectures. But after the acquisition, the OpenSolaris project seemed to end (I don’t know specifics) but several organizations carried on with distributions / forks of OpenSolaris.
On 9/23/16, 10:49 AM, "Python-Dev on behalf of Guido van Rossum" <python-dev-bounces+david.c.stewart=intel.com@python.org on behalf of guido@python.org> wrote:
What on earth is OpenIndiana? Its website is a mystery of buzzwords and PR vagueness:
"openindiana Community-driven Illumos Distribution"
"What is illumos ?
From the illumos developer’s guide: “illumos is a consolidation of software that forms the core of an Operating System. It includes the kernel, device drivers, core system libraries, and utilities. It is the home of many technologies include ZFS, DTrace, Zones, ctf, [...]"
"The “Hipster” branch
Hipster is a codename for rapidly moving development branch of OpenIndiana and users might experience occasional breakages or problems. Hipster is using rolling-release model and only publishes installation ISOs once in a while. Every ISO release will be announced via mailing list and ..."
That didn't exactly answer my questions. Clearly they don't care about anyone who isn't already a user of openindiana or illumos. So I propose that we shouldn't care about them either.
On Fri, Sep 23, 2016 at 1:33 AM, Victor Stinner <victor.stinner@gmail.com> wrote: > Hi, > > My question is simple: do we officially support Solaris and/or OpenIndiana? > > Jesus Cea runs an OpenIndiana buildbot slave: > http://buildbot.python.org/all/buildslaves/cea-indiana-x86 > "Open Indiana 32 bits" > > The platform module of Python says "Solaris-2.11", I don't know the > exact OpenIndiana version. > > A lot of unit tests fail on this buildbot with MemoryError. I guess > that it's related to Solaris which doesn't allow overcommit > (allocating more memory than available memory on the system), or more > simply because the slave has not enough memory. > > There is now an issue which seems specific to OpenIndiana: > http://bugs.python.org/issue27847 > > It might impact Solaris as well, but the Solaris buildbot is offline > since "684 builds". > > Five years ago, I reported a bug because the curses module of Python 3 > doesn't build on Solaris nor OpenIndiana anymore. It seems like the > bug was not fixed, and the issue is still open: > http://bugs.python.org/issue13552 > > So my question is if we officially support Solaris and/or OpenIndiana. > If yes, how can we fix issues when we only have buildbot slave which > has memory errors, and no SSH access to this server? > > Solaris doesn't seem to be officially supported in Python, so I > suggest to drop the OpenIndiana buildbot (which is failing since at > least 2 years) and close all Solaris issues as "WONTFIX". > > Victor > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/david.c.stewart%40intel.c...
-- --Guido van Rossum (python.org/~guido)
I work for Joyent (joyent.com) now, which employs a number of devs that work on illumos (illumos.org). We also provide cloud infrastructure. Would it help if we offered one or more instances (VMs) on which to run buildbot slaves (and on which volunteers for bug fixing could hack)? I know a lot of people in the illumos community would be quite sad to have it dropped as a core Python plat. Guido, Yes you are correct that Oracle owns the Solaris brand. tl;dr history if you care: - sunos -> Solaris - Sun open sources Solaris, called OpenSolaris (2005) - Oracle acquires Sun and closes Solaris (Aug 2010). Shortly after, the community forks OpenSolaris and calls it illumos (Sep 2010) - OpenIndiana is a distro of illumos (somewhat similar to how Ubuntu is a distro of Linux). Other distros are SmartOS (the one Joyent works on), and OmniOS. - Oracle continues work on Solaris, releasing "Solaris 11 Express". I've no real numbers of usage of illumos vs Solaris 11 vs others. Cheers, Trent p.s. I hear that Jesus is also in contact with some of the illumos-devs on IRC (and perhaps email). I hope we can help there.
Thanks for the reality check Trent! I think if enough people with core committer bits want to keep supporting Solaris / Illumos / OpenIndiana / other variants that's fine, but I don't think that just having some VMs to test on is enough -- we also need people who can fix problems if those buildbots start failing, and that requires pretty specialized knowledge. Plus of course we won't know if fixing it for OpenIndiana will also fix it for Solaris 11 Express or for other Illumos forks. (For Linux it's easier to assess these things because so many people in open source use Linux and its many forks.) On Mon, Sep 26, 2016 at 3:32 PM, Trent Mick <trentm@gmail.com> wrote:
I work for Joyent (joyent.com) now, which employs a number of devs that work on illumos (illumos.org). We also provide cloud infrastructure. Would it help if we offered one or more instances (VMs) on which to run buildbot slaves (and on which volunteers for bug fixing could hack)? I know a lot of people in the illumos community would be quite sad to have it dropped as a core Python plat.
Guido, Yes you are correct that Oracle owns the Solaris brand.
tl;dr history if you care: - sunos -> Solaris - Sun open sources Solaris, called OpenSolaris (2005) - Oracle acquires Sun and closes Solaris (Aug 2010). Shortly after, the community forks OpenSolaris and calls it illumos (Sep 2010) - OpenIndiana is a distro of illumos (somewhat similar to how Ubuntu is a distro of Linux). Other distros are SmartOS (the one Joyent works on), and OmniOS. - Oracle continues work on Solaris, releasing "Solaris 11 Express".
I've no real numbers of usage of illumos vs Solaris 11 vs others.
Cheers, Trent
p.s. I hear that Jesus is also in contact with some of the illumos-devs on IRC (and perhaps email). I hope we can help there.
-- --Guido van Rossum (python.org/~guido)
On Mon, 26 Sep 2016 at 15:38 Guido van Rossum <guido@python.org> wrote:
Thanks for the reality check Trent! I think if enough people with core committer bits want to keep supporting Solaris / Illumos / OpenIndiana / other variants that's fine, but I don't think that just having some VMs to test on is enough -- we also need people who can fix problems if those buildbots start failing, and that requires pretty specialized knowledge. Plus of course we won't know if fixing it for OpenIndiana will also fix it for Solaris 11 Express or for other Illumos forks. (For Linux it's easier to assess these things because so many people in open source use Linux and its many forks.)
The official requirement to support a platform is a stable buildbot and a core dev to keep the support up: https://www.python.org/dev/peps/pep-0011/#supporting-platforms. Victor has asked that the OpenIndiana buildbot be removed from the stable pool as it consistently throws MemoryError which means its support is not improving. If Trent is willing to maintain a buildbot in a Joyent VM that at least takes care of that part, but it still requires Jesus to volunteer to keep the support up if it's going to be supported for free. Otherwise Joyent could consider contracting with one of the various core devs who happen to be consultants to help maintain the support. At minimum, though, a new buildbot could go into the unstable pool so illumos devs can keep an eye on when things break to try and get platform-independent changes upstreamed that happen to help illumos (e.g. no #ifdef changes specific to illumos, but if something just needed to be made more robust and it happens to help illumos that's typically fine).
On Mon, Sep 26, 2016 at 3:32 PM, Trent Mick <trentm@gmail.com> wrote:
I work for Joyent (joyent.com) now, which employs a number of devs that work on illumos (illumos.org). We also provide cloud infrastructure. Would it help if we offered one or more instances (VMs) on which to run buildbot slaves (and on which volunteers for bug fixing could hack)? I know a lot of people in the illumos community would be quite sad to have it dropped as a core Python plat.
Guido, Yes you are correct that Oracle owns the Solaris brand.
tl;dr history if you care: - sunos -> Solaris - Sun open sources Solaris, called OpenSolaris (2005) - Oracle acquires Sun and closes Solaris (Aug 2010). Shortly after, the community forks OpenSolaris and calls it illumos (Sep 2010) - OpenIndiana is a distro of illumos (somewhat similar to how Ubuntu is a distro of Linux). Other distros are SmartOS (the one Joyent works on), and OmniOS. - Oracle continues work on Solaris, releasing "Solaris 11 Express".
I've no real numbers of usage of illumos vs Solaris 11 vs others.
Cheers, Trent
p.s. I hear that Jesus is also in contact with some of the illumos-devs on IRC (and perhaps email). I hope we can help there.
-- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org
Hi, Is there anything new about Solaris or OpenIndiana since September? Right now, it seems like the cea-indiana-x86 buildbot slave is offline since longer than 54 days. Oracle decided to stop Solaris 12 development: https://arstechnica.com/information-technology/2017/01/oracle-sort-of-confir... I'm not opposed to help if someone provides patches to fix Solaris issues, but it seems like no one wants to do this job. So I suggest to drop official Solaris support, but I don't propose to remove the C code specific to Solaris. In practice, I suggest to remove Solaris and OpenIndiana buildbots since they are broken for months and are more annoying than useful. Victor 2016-09-27 0:54 GMT+02:00 Brett Cannon <brett@python.org>:
On Mon, 26 Sep 2016 at 15:38 Guido van Rossum <guido@python.org> wrote:
Thanks for the reality check Trent! I think if enough people with core committer bits want to keep supporting Solaris / Illumos / OpenIndiana / other variants that's fine, but I don't think that just having some VMs to test on is enough -- we also need people who can fix problems if those buildbots start failing, and that requires pretty specialized knowledge. Plus of course we won't know if fixing it for OpenIndiana will also fix it for Solaris 11 Express or for other Illumos forks. (For Linux it's easier to assess these things because so many people in open source use Linux and its many forks.)
The official requirement to support a platform is a stable buildbot and a core dev to keep the support up: https://www.python.org/dev/peps/pep-0011/#supporting-platforms. Victor has asked that the OpenIndiana buildbot be removed from the stable pool as it consistently throws MemoryError which means its support is not improving. If Trent is willing to maintain a buildbot in a Joyent VM that at least takes care of that part, but it still requires Jesus to volunteer to keep the support up if it's going to be supported for free. Otherwise Joyent could consider contracting with one of the various core devs who happen to be consultants to help maintain the support.
At minimum, though, a new buildbot could go into the unstable pool so illumos devs can keep an eye on when things break to try and get platform-independent changes upstreamed that happen to help illumos (e.g. no #ifdef changes specific to illumos, but if something just needed to be made more robust and it happens to help illumos that's typically fine).
On Mon, Sep 26, 2016 at 3:32 PM, Trent Mick <trentm@gmail.com> wrote:
I work for Joyent (joyent.com) now, which employs a number of devs that work on illumos (illumos.org). We also provide cloud infrastructure. Would it help if we offered one or more instances (VMs) on which to run buildbot slaves (and on which volunteers for bug fixing could hack)? I know a lot of people in the illumos community would be quite sad to have it dropped as a core Python plat.
Guido, Yes you are correct that Oracle owns the Solaris brand.
tl;dr history if you care: - sunos -> Solaris - Sun open sources Solaris, called OpenSolaris (2005) - Oracle acquires Sun and closes Solaris (Aug 2010). Shortly after, the community forks OpenSolaris and calls it illumos (Sep 2010) - OpenIndiana is a distro of illumos (somewhat similar to how Ubuntu is a distro of Linux). Other distros are SmartOS (the one Joyent works on), and OmniOS. - Oracle continues work on Solaris, releasing "Solaris 11 Express".
I've no real numbers of usage of illumos vs Solaris 11 vs others.
Cheers, Trent
p.s. I hear that Jesus is also in contact with some of the illumos-devs on IRC (and perhaps email). I hope we can help there.
-- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.co...
On 08/02/17 11:24, Victor Stinner wrote:
So I suggest to drop official Solaris support, but I don't propose to remove the C code specific to Solaris. In practice, I suggest to remove Solaris and OpenIndiana buildbots since they are broken for months and are more annoying than useful.
Give me a week to move this forward. Last hope. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
On 08/02/17 11:24, Victor Stinner wrote:
So I suggest to drop official Solaris support, but I don't propose to remove the C code specific to Solaris. In practice, I suggest to remove Solaris and OpenIndiana buildbots since they are broken for months and are more annoying than useful.
The main issue is that something wrong is going on with buildbot. From time to time, it eats gigabytes of RAM (last time, 64GB) and kills the machine. maybe once per week. This is not very welcomed by my host and his reaction is to shutdown the solaris "zone" because we don't "behave" and this is impacting production system. I am trying to convince him to launch buildbot process tree with an "ulimit" to protect the machine. Lets see. Sorry. Thanks for your patience. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
On 08/02/17 16:18, Jesus Cea wrote:
I am trying to convince him to launch buildbot process tree with an "ulimit" to protect the machine. Lets see.
Sorry. Thanks for your patience.
I am launching now the buildbot with a limit of 1GB *PER PROCESS*. At least, when the memory skyrockets it will die without impacting the rest of the machine. Unless it does a fork-bomb... Backlog is huge. That will be useful to stress the buildbot and, hopefuly, make it fails faster. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
On 08/02/17 17:06, Jesus Cea wrote:
On 08/02/17 16:18, Jesus Cea wrote:
I am trying to convince him to launch buildbot process tree with an "ulimit" to protect the machine. Lets see.
Sorry. Thanks for your patience.
I am launching now the buildbot with a limit of 1GB *PER PROCESS*. At least, when the memory skyrockets it will die without impacting the rest of the machine. Unless it does a fork-bomb...
Backlog is huge. That will be useful to stress the buildbot and, hopefuly, make it fails faster.
Checking the mailing list archives, I am seen Openindiana buildbot memory issues since 2011, at least. <https://mail.python.org/pipermail//python-dev/2011-September/113532.html>. It was never triaged. I am getting mercurial errors because some incompatibility with current release <http://buildbot.python.org/all/builders/x86%20OpenIndiana%203.5/builds/79/steps/touch/logs/stdio>. Since we are moving to github in a couple of days, I will wait until that time to keep pursuing this. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
2017-02-08 15:14 GMT+01:00 Jesus Cea <jcea@jcea.es>:
On 08/02/17 11:24, Victor Stinner wrote:
So I suggest to drop official Solaris support, but I don't propose to remove the C code specific to Solaris. In practice, I suggest to remove Solaris and OpenIndiana buildbots since they are broken for months and are more annoying than useful.
Give me a week to move this forward. Last hope.
Any update? "One week" was one month ago :-) Victor
participants (6)
-
Brett Cannon -
Guido van Rossum -
Jesus Cea -
Stewart, David C -
Trent Mick -
Victor Stinner