Re: Python versions (redux)

2014-07-17 Thread Joe Smith
Me as well- thanks for bringing this up! On Thu, Jul 17, 2014 at 12:32 PM, Bill Farner 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 > wrote: > > > Only reason I c

Re: Python versions (redux)

2014-07-17 Thread Bill Farner
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 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 disco

Re: Python versions (redux)

2014-07-17 Thread Bhuvan Arumugam
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 i

Re: Python versions (redux)

2014-07-17 Thread Kevin Sweeney
+1 to dropping 2.6 On Thu, Jul 17, 2014 at 11:46 AM, Mark Chu-Carroll 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-o09

Re: Python versions

2014-04-29 Thread Mark Chu-Carroll
Per Brian's reply, it turns out that we can maintain perfect backwards compatibility for free, by using a library we already depend on. -Mark On Tue, Apr 29, 2014 at 12:55 PM, Alexius Ludeman wrote: > -1 > > I would highly recommend trying to be compatible with python 2.6. RHEL/OEL > 6u3-6

Re: Python versions

2014-04-29 Thread Alexius Ludeman
-1 I would highly recommend trying to be compatible with python 2.6. RHEL/OEL 6u3-6u5 are still on python 2.6... On Tue, Apr 29, 2014 at 7:46 AM, Bill Farner wrote: > +1 > > On Tuesday, April 29, 2014, Jake Farrell wrote: > > > +1 to keeping as current as possible and not introducing workaro

Re: Python versions

2014-04-29 Thread Brian Wickman
Please use twitter.common.lang Compatibility.exec_function: https://github.com/twitter/commons/blob/master/src/python/twitter/common/lang/__init__.py#L122 Happy on 2.x and 3.x (even 2.6.x) On Tue, Apr 29, 2014 at 6:31 AM, Mark Chu-Carroll wrote: > Folks: > > For one of the client changes I'm w

Re: Python versions

2014-04-29 Thread Dan Norris
+1. I can update AURORA-227 to enforce Python 2.7 as the minimum version ( https://reviews.apache.org/r/18537/). On Tue, Apr 29, 2014 at 10:46 AM, Bill Farner wrote: > +1 > > On Tuesday, April 29, 2014, Jake Farrell wrote: > > > +1 to keeping as current as possible and not introducing workaro

Re: Python versions

2014-04-29 Thread Bill Farner
+1 On Tuesday, April 29, 2014, Jake Farrell wrote: > +1 to keeping as current as possible and not introducing workarounds for > older os variants. Python 2.7 is the default on Ubuntu 12.04 and OS X which > is what a majority of people will use for testing/development and our > Vagrant images are

Re: Python versions

2014-04-29 Thread Jake Farrell
+1 to keeping as current as possible and not introducing workarounds for older os variants. Python 2.7 is the default on Ubuntu 12.04 and OS X which is what a majority of people will use for testing/development and our Vagrant images are built around this as well. AURORA-227 introduces a check for