[
https://issues.apache.org/jira/browse/MESOS-8882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464396#comment-16464396
]
Armand Grillet commented on MESOS-8882:
---------------------------------------
[~andschwa] Thank you for your feedback and first patch! I have edited the
ticket following your first comment.
Yes, pyenv is still the standard way to go for versioning.
Will take a look at #66964 during the next days, I have read the description
and testing done and I am now looking at how to handle {{pylint}} with the
situation we will have.
> Add Python 3 as a dependency and use it for our Python codebase
> ---------------------------------------------------------------
>
> Key: MESOS-8882
> URL: https://issues.apache.org/jira/browse/MESOS-8882
> Project: Mesos
> Issue Type: Epic
> Components: cli, python api
> Reporter: Armand Grillet
> Priority: Major
>
> As mentioned by [~andschwa] [2 weeks
> ago|https://mesos.slack.com/archives/C1LPTK50T/p1524165786000521], 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.
> The support scripts and CLI can be updated independently of the switch if we
> assume that most of our devs have Python 2 and 3 installed on their machines.
> The Python can be updated last as they should not be used anymore, in favor
> of our V1 API.
> This new dependency will require 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 it could cause any issue on their
> side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
