You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by Mark Chu-Carroll <mc...@apache.org> on 2014/07/17 20:46:14 UTC
Python versions (redux)
A couple of months ago, we had a discussion about which python versions to
support. (See
http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201404.mbox/%3CCAFGkSCk71%2BziUQCsnMfStr-ucrT52DLEgBfHA-o097683PstLQ%40mail.gmail.com%3E
to refresh your memory.)
At the time, we punted on it, because we had a convenient workaround. But
python version issues have continued to pop up from time to time. In
particular, we've had issues like the current
https://issues.apache.org/jira/browse/AURORA-585.
The question that I'd like to put forward is: how much effort is it work to
continue to support Python 2.6? The Python maintainers are no longer
maintaining 2.6 - the download page for the last release of 2.6 says:
"With the 2.6.9 release, and five years after its first release, the
Python 2.6 series is now officially retired. All official maintenance for
Python 2.6, including security patches, has ended. For ongoing maintenance
releases, please see the Python 2.7 series. The NEWS file lists every
change in each alpha, beta, release candidate, and final release of Python
2.6."
We certainly *can* continue to support Python2.6, but it's likely to be a
non-trivial effort. Is it worth it?
(Full disclosure, in case it's not obvious: I think as a provider of a
distributed computing platform, continuing to support a python interpreter
that won't even get security fixes is not a good idea. I'm in favor of
dropping 2.6.)
-Mark
Re: Python versions (redux)
Posted by Kevin Sweeney <ke...@apache.org>.
+1 to dropping 2.6
On Thu, Jul 17, 2014 at 11:46 AM, Mark Chu-Carroll <mc...@apache.org>
wrote:
> A couple of months ago, we had a discussion about which python versions to
> support. (See
>
> http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201404.mbox/%3CCAFGkSCk71%2BziUQCsnMfStr-ucrT52DLEgBfHA-o097683PstLQ%40mail.gmail.com%3E
> to refresh your memory.)
>
> At the time, we punted on it, because we had a convenient workaround. But
> python version issues have continued to pop up from time to time. In
> particular, we've had issues like the current
> https://issues.apache.org/jira/browse/AURORA-585.
>
> The question that I'd like to put forward is: how much effort is it work to
> continue to support Python 2.6? The Python maintainers are no longer
> maintaining 2.6 - the download page for the last release of 2.6 says:
> "With the 2.6.9 release, and five years after its first release, the
> Python 2.6 series is now officially retired. All official maintenance for
> Python 2.6, including security patches, has ended. For ongoing maintenance
> releases, please see the Python 2.7 series. The NEWS file lists every
> change in each alpha, beta, release candidate, and final release of Python
> 2.6."
>
> We certainly *can* continue to support Python2.6, but it's likely to be a
> non-trivial effort. Is it worth it?
>
> (Full disclosure, in case it's not obvious: I think as a provider of a
> distributed computing platform, continuing to support a python interpreter
> that won't even get security fixes is not a good idea. I'm in favor of
> dropping 2.6.)
>
> -Mark
>
Re: Python versions (redux)
Posted by Joe Smith <ya...@gmail.com>.
Me as well- thanks for bringing this up!
On Thu, Jul 17, 2014 at 12:32 PM, Bill Farner <wf...@apache.org> wrote:
> Bhuvan's link [2] was the clincher for me. +1 to dropping support, as the
> python developers have.
>
> -=Bill
>
>
> On Thu, Jul 17, 2014 at 12:11 PM, Bhuvan Arumugam <bh...@apache.org>
> wrote:
>
> > Only reason I could think of supporting py26 is to support rhel6.x
> > customers. Now that rhel7 is out [1], it make sense to discontinue
> > support for py26. We should document it in supported platforms though.
> > We should add a pointer for rhel6.x customers to upgrade python.
> >
> > It also make sense as py26 is already eol [2].
> >
> > That said, +1 to discontinue support for py26.
> >
> > [1]
> >
> http://www.redhat.com/about/news/press-archive/2014/6/red-hat-unveils-rhel-7
> > [2]
> > https://mail.python.org/pipermail/python-dev/2013-September/128287.html
> >
> >
> > On Thu, Jul 17, 2014 at 11:46 AM, Mark Chu-Carroll
> > <mc...@apache.org> wrote:
> > > A couple of months ago, we had a discussion about which python versions
> > to
> > > support. (See
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201404.mbox/%3CCAFGkSCk71%2BziUQCsnMfStr-ucrT52DLEgBfHA-o097683PstLQ%40mail.gmail.com%3E
> > > to refresh your memory.)
> > >
> > > At the time, we punted on it, because we had a convenient workaround.
> But
> > > python version issues have continued to pop up from time to time. In
> > > particular, we've had issues like the current
> > > https://issues.apache.org/jira/browse/AURORA-585.
> > >
> > > The question that I'd like to put forward is: how much effort is it
> work
> > to
> > > continue to support Python 2.6? The Python maintainers are no longer
> > > maintaining 2.6 - the download page for the last release of 2.6 says:
> > > "With the 2.6.9 release, and five years after its first release, the
> > > Python 2.6 series is now officially retired. All official maintenance
> for
> > > Python 2.6, including security patches, has ended. For ongoing
> > maintenance
> > > releases, please see the Python 2.7 series. The NEWS file lists every
> > > change in each alpha, beta, release candidate, and final release of
> > Python
> > > 2.6."
> > >
> > > We certainly *can* continue to support Python2.6, but it's likely to
> be a
> > > non-trivial effort. Is it worth it?
> > >
> > > (Full disclosure, in case it's not obvious: I think as a provider of a
> > > distributed computing platform, continuing to support a python
> > interpreter
> > > that won't even get security fixes is not a good idea. I'm in favor of
> > > dropping 2.6.)
> > >
> > > -Mark
> >
> >
> >
> > --
> > Regards,
> > Bhuvan Arumugam
> > www.livecipher.com
> >
>
Re: Python versions (redux)
Posted by Bill Farner <wf...@apache.org>.
Bhuvan's link [2] was the clincher for me. +1 to dropping support, as the
python developers have.
-=Bill
On Thu, Jul 17, 2014 at 12:11 PM, Bhuvan Arumugam <bh...@apache.org> wrote:
> Only reason I could think of supporting py26 is to support rhel6.x
> customers. Now that rhel7 is out [1], it make sense to discontinue
> support for py26. We should document it in supported platforms though.
> We should add a pointer for rhel6.x customers to upgrade python.
>
> It also make sense as py26 is already eol [2].
>
> That said, +1 to discontinue support for py26.
>
> [1]
> http://www.redhat.com/about/news/press-archive/2014/6/red-hat-unveils-rhel-7
> [2]
> https://mail.python.org/pipermail/python-dev/2013-September/128287.html
>
>
> On Thu, Jul 17, 2014 at 11:46 AM, Mark Chu-Carroll
> <mc...@apache.org> wrote:
> > A couple of months ago, we had a discussion about which python versions
> to
> > support. (See
> >
> http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201404.mbox/%3CCAFGkSCk71%2BziUQCsnMfStr-ucrT52DLEgBfHA-o097683PstLQ%40mail.gmail.com%3E
> > to refresh your memory.)
> >
> > At the time, we punted on it, because we had a convenient workaround. But
> > python version issues have continued to pop up from time to time. In
> > particular, we've had issues like the current
> > https://issues.apache.org/jira/browse/AURORA-585.
> >
> > The question that I'd like to put forward is: how much effort is it work
> to
> > continue to support Python 2.6? The Python maintainers are no longer
> > maintaining 2.6 - the download page for the last release of 2.6 says:
> > "With the 2.6.9 release, and five years after its first release, the
> > Python 2.6 series is now officially retired. All official maintenance for
> > Python 2.6, including security patches, has ended. For ongoing
> maintenance
> > releases, please see the Python 2.7 series. The NEWS file lists every
> > change in each alpha, beta, release candidate, and final release of
> Python
> > 2.6."
> >
> > We certainly *can* continue to support Python2.6, but it's likely to be a
> > non-trivial effort. Is it worth it?
> >
> > (Full disclosure, in case it's not obvious: I think as a provider of a
> > distributed computing platform, continuing to support a python
> interpreter
> > that won't even get security fixes is not a good idea. I'm in favor of
> > dropping 2.6.)
> >
> > -Mark
>
>
>
> --
> Regards,
> Bhuvan Arumugam
> www.livecipher.com
>
Re: Python versions (redux)
Posted by Bhuvan Arumugam <bh...@apache.org>.
Only reason I could think of supporting py26 is to support rhel6.x
customers. Now that rhel7 is out [1], it make sense to discontinue
support for py26. We should document it in supported platforms though.
We should add a pointer for rhel6.x customers to upgrade python.
It also make sense as py26 is already eol [2].
That said, +1 to discontinue support for py26.
[1] http://www.redhat.com/about/news/press-archive/2014/6/red-hat-unveils-rhel-7
[2] https://mail.python.org/pipermail/python-dev/2013-September/128287.html
On Thu, Jul 17, 2014 at 11:46 AM, Mark Chu-Carroll
<mc...@apache.org> wrote:
> A couple of months ago, we had a discussion about which python versions to
> support. (See
> http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201404.mbox/%3CCAFGkSCk71%2BziUQCsnMfStr-ucrT52DLEgBfHA-o097683PstLQ%40mail.gmail.com%3E
> to refresh your memory.)
>
> At the time, we punted on it, because we had a convenient workaround. But
> python version issues have continued to pop up from time to time. In
> particular, we've had issues like the current
> https://issues.apache.org/jira/browse/AURORA-585.
>
> The question that I'd like to put forward is: how much effort is it work to
> continue to support Python 2.6? The Python maintainers are no longer
> maintaining 2.6 - the download page for the last release of 2.6 says:
> "With the 2.6.9 release, and five years after its first release, the
> Python 2.6 series is now officially retired. All official maintenance for
> Python 2.6, including security patches, has ended. For ongoing maintenance
> releases, please see the Python 2.7 series. The NEWS file lists every
> change in each alpha, beta, release candidate, and final release of Python
> 2.6."
>
> We certainly *can* continue to support Python2.6, but it's likely to be a
> non-trivial effort. Is it worth it?
>
> (Full disclosure, in case it's not obvious: I think as a provider of a
> distributed computing platform, continuing to support a python interpreter
> that won't even get security fixes is not a good idea. I'm in favor of
> dropping 2.6.)
>
> -Mark
--
Regards,
Bhuvan Arumugam
www.livecipher.com