Hi all,
We now have ongoing work to update all our Python components to Python 3
except for the bindings. We have taken care of the build system to work
with both the Python 2 and 3 codebase thus the bindings do not need to be
deprecated/updated before Python 2 EOL (i.e. 2020, and even then I do n
> On May 9, 2018, at 11:51 AM, Andrew Schwartzmeyer
> wrote:
>
> Hi all,
>
> There are two parallel efforts underway that would both benefit from
> officially deprecating (and then removing) the Python bindings. The first
> effort is the move to the CMake system: adding support to generate
Andrew,
Is it one of the reasons for deprecating this binding the lack of
interest of Mesos community? If the answer is yes, let me try to boost
the maintenance of this biding.
--
Javi Roman
Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog:
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 swit
One of the production users that I know who used to depend on python
bindings were https://github.com/douban.
Also, apache aurora used to have an executor that depended on python
bindings.
I don't know what their dependencies are these days w.r.t python bindings.
On Wed, May 9, 2018 at 11:51 AM,
Hi all,
There are two parallel efforts underway that would both benefit from
officially deprecating (and then removing) the Python bindings. The
first effort is the move to the CMake system: adding support to generate
the Python bindings was investigated but paused (see MESOS-8118), and
the s
6 matches
Mail list logo