Hi, within SAP, we still use the Python bindings for our own productive Mesos framework. There a multiple different pure Python implementations available but especially this wide choice, different capabilities, unclear update frequencies, available documentation and mixed quality makes the switch hard and brings a lot of uncertainties. With the Python binding we had always a reliable pice software that was part of Mesos and therefore covered somehow with testing and included in release decisions.
I understand the motivation behind the deprecation and removal. But I'm afraid of the drop of the 'official' Python bind as it will probably deter people to build Mesos frameworks with Python. Maybe it would make sense to promote one implementation as recommended and include it into testing and release decisions but I see also the point to give flexibility and choices. Best regards, Christoph Christoph Heer, SAP SE, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Bill McDermott (CEO), Robert Enslin, Adaire Fox-Martin, Christian Klein, Michael Kleinemeier, Bernd Leukert, Jennifer Morgan, Luka Mucic, Stefan Ries Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim HRB 719915 This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
