mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Schwartzmeyer (JIRA)" <>
Subject [jira] [Commented] (MESOS-8882) Add Python 3 as a dependency and use it for our Python codebase
Date Fri, 04 May 2018 20:48:00 GMT


Andrew Schwartzmeyer commented on MESOS-8882:

All right, I tried out {{futurize}} and it seems promising to at least make out support scripts
single-source Python 2 and 3 compatible. If it works out well enough, then we can at least
fix MESOS-7658 (which I consider a very rude issue) without forcing the adoption of Python
3 as a dependency immediately. WIP patch is [review #66964|].

> Add Python 3 as a dependency and use it for our Python codebase
> ---------------------------------------------------------------
>                 Key: MESOS-8882
>                 URL:
>             Project: Mesos
>          Issue Type: Epic
>          Components: cli, python api
>            Reporter: Armand Grillet
>            Priority: Major
> As mentioned by [~andschwa] [2 weeks ago|],
nothing new should use Python 2. [~cinchurge] and [~ArmandGrillet] are currently working on
the CLI while being shepherded by [~klueska] and, as we plan to do more work on it soon, mentioned
again today that it would be a good time to start using Python 3 in our codebase.
> We use Python 2 in four areas of the Mesos codebase:
> * In the support scripts.
> * In the new CLI.
> * In the new Mesos Python package.
> * In the Python bindings.
> All these areas need to be updated if we switch to Python 3, except maybe the Python
bindings that should not be used anymore, in favor of our V1 API.
> This new dependency would also require some changes in our documentation regarding how
to build Python. As it will be a change for Mesos devs, we have to express the reasons behind
this change and check if this change could cause any issue on their side.

This message was sent by Atlassian JIRA

View raw message