Upgrading our support scripts to Python 3

[Armand Grillet <ag...@mesosphere.io>]

Hi all,

Python 2.7 will retire on January 1, 2020 and we currently use it for
our support scripts, our Python bindings, and our new CLI.

Starting July 1, 2018 you will need to have Python 3.6 on your computer
in order to use the support scripts. It is available on all the
operating systems we support and even preinstalled on most recent Linux
distributions. We're making this change due to issues with our support
scripts on Windows that have been fixed with Python 3.

If you already have Python 3.6 installed on your machine, great.
Otherwise, you will see a deprecation message when you use the support
scripts and the related git hooks. Don't worry, these messages and the
switch to Python 3 do not change how the scripts work.

We now have Python 3 support scripts alongside the existing ones. Having
a duplicated codebase is not sustainable and we thus plan on deprecating
the Python 2 support scripts by July 1st. We want to have a few weeks to
test these new scripts thoroughly and let you install Python 3.6, this
is why we have decided to have both codebases for a while.

If you want to use the new scripts, set in your environment the variable
`MESOS_SUPPORT_PYTHON` to `3` and run again the bash support script
`build-virtualenv`. You will then use the Python 3 scripts by default.

If you have any questions, please answer to this thread or join the
Mesos Slack channel #python3.

PS: This Python 3 switch does not apply to the rest of our codebase yet.
As we have seen in a previous thread, some developers still rely on the
Python 2 bindings and we do not want to disturb that.

-- 
Armand Grillet
Software Engineer, Mesosphere

Re: Upgrading our support scripts to Python 3

[Armand Grillet <ag...@mesosphere.io>]

Hi Vinod,

Not yet, it is part of our Python3 epic
<https://issues.apache.org/jira/browse/MESOS-8882> tickets and I'll take
care of it
in the coming weeks.

2018-05-25 16:23 GMT+02:00 Vinod Kone <vi...@gmail.com>:

> Have we turned python3 on in our CI? Would be great to test.
>
> Sent from my phone
>
> > On May 24, 2018, at 11:26 PM, Armand Grillet <ag...@mesosphere.io>
> wrote:
> >
> > Hi all,
> >
> > Python 2.7 will retire on January 1, 2020 and we currently use it for
> > our support scripts, our Python bindings, and our new CLI.
> >
> > Starting July 1, 2018 you will need to have Python 3.6 on your computer
> > in order to use the support scripts. It is available on all the
> > operating systems we support and even preinstalled on most recent Linux
> > distributions. We're making this change due to issues with our support
> > scripts on Windows that have been fixed with Python 3.
> >
> > If you already have Python 3.6 installed on your machine, great.
> > Otherwise, you will see a deprecation message when you use the support
> > scripts and the related git hooks. Don't worry, these messages and the
> > switch to Python 3 do not change how the scripts work.
> >
> > We now have Python 3 support scripts alongside the existing ones. Having
> > a duplicated codebase is not sustainable and we thus plan on deprecating
> > the Python 2 support scripts by July 1st. We want to have a few weeks to
> > test these new scripts thoroughly and let you install Python 3.6, this
> > is why we have decided to have both codebases for a while.
> >
> > If you want to use the new scripts, set in your environment the variable
> > `MESOS_SUPPORT_PYTHON` to `3` and run again the bash support script
> > `build-virtualenv`. You will then use the Python 3 scripts by default.
> >
> > If you have any questions, please answer to this thread or join the
> > Mesos Slack channel #python3.
> >
> > PS: This Python 3 switch does not apply to the rest of our codebase yet.
> > As we have seen in a previous thread, some developers still rely on the
> > Python 2 bindings and we do not want to disturb that.
> >
> > --
> > Armand Grillet
> > Software Engineer, Mesosphere
>



-- 
Armand Grillet
Software Engineer, Mesosphere

Re: Upgrading our support scripts to Python 3

[Vinod Kone <vi...@gmail.com>]

Have we turned python3 on in our CI? Would be great to test. 

Sent from my phone

> On May 24, 2018, at 11:26 PM, Armand Grillet <ag...@mesosphere.io> wrote:
> 
> Hi all,
> 
> Python 2.7 will retire on January 1, 2020 and we currently use it for
> our support scripts, our Python bindings, and our new CLI.
> 
> Starting July 1, 2018 you will need to have Python 3.6 on your computer
> in order to use the support scripts. It is available on all the
> operating systems we support and even preinstalled on most recent Linux
> distributions. We're making this change due to issues with our support
> scripts on Windows that have been fixed with Python 3.
> 
> If you already have Python 3.6 installed on your machine, great.
> Otherwise, you will see a deprecation message when you use the support
> scripts and the related git hooks. Don't worry, these messages and the
> switch to Python 3 do not change how the scripts work.
> 
> We now have Python 3 support scripts alongside the existing ones. Having
> a duplicated codebase is not sustainable and we thus plan on deprecating
> the Python 2 support scripts by July 1st. We want to have a few weeks to
> test these new scripts thoroughly and let you install Python 3.6, this
> is why we have decided to have both codebases for a while.
> 
> If you want to use the new scripts, set in your environment the variable
> `MESOS_SUPPORT_PYTHON` to `3` and run again the bash support script
> `build-virtualenv`. You will then use the Python 3 scripts by default.
> 
> If you have any questions, please answer to this thread or join the
> Mesos Slack channel #python3.
> 
> PS: This Python 3 switch does not apply to the rest of our codebase yet.
> As we have seen in a previous thread, some developers still rely on the
> Python 2 bindings and we do not want to disturb that.
> 
> -- 
> Armand Grillet
> Software Engineer, Mesosphere

Re: Upgrading our support scripts to Python 3

[Andrew Schwartzmeyer <an...@schwartzmeyer.com>]

Thank you Armand for all your work doing this!

It's far from a pleasant task, but it's a necessary one.

On 05/24/2018 11:26 pm, Armand Grillet wrote:
> Hi all,
> 
> Python 2.7 will retire on January 1, 2020 and we currently use it for
> our support scripts, our Python bindings, and our new CLI.
> 
> Starting July 1, 2018 you will need to have Python 3.6 on your computer
> in order to use the support scripts. It is available on all the
> operating systems we support and even preinstalled on most recent Linux
> distributions. We're making this change due to issues with our support
> scripts on Windows that have been fixed with Python 3.
> 
> If you already have Python 3.6 installed on your machine, great.
> Otherwise, you will see a deprecation message when you use the support
> scripts and the related git hooks. Don't worry, these messages and the
> switch to Python 3 do not change how the scripts work.
> 
> We now have Python 3 support scripts alongside the existing ones. 
> Having
> a duplicated codebase is not sustainable and we thus plan on 
> deprecating
> the Python 2 support scripts by July 1st. We want to have a few weeks 
> to
> test these new scripts thoroughly and let you install Python 3.6, this
> is why we have decided to have both codebases for a while.
> 
> If you want to use the new scripts, set in your environment the 
> variable
> `MESOS_SUPPORT_PYTHON` to `3` and run again the bash support script
> `build-virtualenv`. You will then use the Python 3 scripts by default.
> 
> If you have any questions, please answer to this thread or join the
> Mesos Slack channel #python3.
> 
> PS: This Python 3 switch does not apply to the rest of our codebase 
> yet.
> As we have seen in a previous thread, some developers still rely on the
> Python 2 bindings and we do not want to disturb that.