Since we'll be maintaining backwards compatibility with python 2.7, we
can't really use python 3 only language features or reserved keywords
anyways so we should probably just target the lowest common denominator (so
3.4 or 3.5 probably) and then after Python 2 is officially EOL in 2020
perhaps we
On Mon, Mar 18, 2019 at 7:52 PM Michael Shuler
wrote:
> On 3/18/19 9:06 PM, Patrick Bannister wrote:
> > I recommend we pick the longest supported stable release available. That
> > would be Python 3.7, which is planned to get its last release in 2023,
> four
> > years from now.
> > - Python 3.5
On 3/18/19 9:52 PM, Michael Shuler wrote:
> On 3/18/19 9:06 PM, Patrick Bannister wrote:
>> I recommend we pick the longest supported stable release available. That
>> would be Python 3.7, which is planned to get its last release in 2023, four
>> years from now.
>> - Python 3.5 was planned to get i
On 3/18/19 9:06 PM, Patrick Bannister wrote:
> I recommend we pick the longest supported stable release available. That
> would be Python 3.7, which is planned to get its last release in 2023, four
> years from now.
> - Python 3.5 was planned to get its last major release yesterday
> - Python 3.6 i
Hello, I'm resuming work on Python 3 support for cqlsh (CASSANDRA-10190).
As discussed before, the plan for this work is to get it working on Python
3 while keeping it compatible with Python 2.7.
I'd like to settle on a Python 3 release to be our officially supported
tested version. It would be bu
