> On Oct 26, 2017, at 2:50 PM, Tal Liron <[email protected]> wrote:
>
> Just to clarify: we currently support *both* Python 2.6 and Python 2.7. The
> poll is to see if we should continue supporting 2.6.
Thanks for the correction. I didn’t mean that we weren’t supporting
2.7. 8)
—Tom
> You might ask why we supported 2.6 in the first place: this came from our
> long experience working on Cloudify. Many cloud environments are still
> quite old, and many companies still run very old versions of CentOS or
> Debian, which do not come with Python 2.7 out of the box. However, with our
> hand on the pulse it seems that these old OSes are fading away. Since ARIA
> is forward-looking, it may make sense to remove this requirement.
>
> On Thu, Oct 26, 2017 at 1:43 PM, Thomas Nadeau <[email protected]>
> wrote:
>
>>
>> We’ve been considering moving from 2.6 onto the latest 2.7 for
>> some time now,
>> and it looks like its time to seriously consider cutting over. Tal has
>> pointed out
>> numerous times that because of the 2.6 support, we have a lot of extra
>> testing
>> and staging that could be eliminated, plus some other benefits that he
>> might
>> want to elaborate on here.
>>
>> With this in mind, I wanted to take a poll of the community above
>> making this
>> move. I would like to hear from both users and devs as to whether or not
>> this is cool.
>> I’d like to also ask that regardless of your position, that you please
>> indicate a time frame
>> for moving towards 2.7.x because even if you don’t want the project to
>> move, it is
>> going to eventually move on but if there are any gating issues requiring
>> us to
>> take a slower than immediate move here, we need to know and plan for this.
>>
>> Thanks!
>>
>> —Tom
>>
>>
