On Wed, Aug 24, 2016 at 2:09 PM, Allen Wittenauer <[email protected]> wrote:
> > > On Aug 24, 2016, at 1:04 PM, Andrew Wang <[email protected]> > wrote: > > > >> I'm pretty sure you have access to a machine with Python 2.7 though, or > > the means to install it. That's what I meant by "no one runs RHEL6 on > their > > personal dev machine". > > > > Same applies to the alternative OSes. > > ... and with that, you've pretty much convinced me that setting > the minimum to python 2.7 is not worth pursuing. > > "Oh you should go build half of your software over here and the > other half on this other box and then manually merge the results" is not > very user-friendly at all. > > I didn't say you should build half here and half there, I said that you could either: a) run your entire workflow on a more modern machine, that has Python 2.7 via a package manager b) install Python 2.7 via conda Given the presence of conda, I don't see Python 2.7 as that different as any other third-party dependency. For instance, test-patch has all kinds of integrations that aren't available out-of-the-box on RHEL6 like Docker and Gradle. If people can install those, they can definitely also install Python 2.7 via conda.
