Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Kurt's proposal to freeze the 2.7 implementation and offer a Python 3 implementation alongside it appeals to my desire to free ourselves of design choices made for the sake of Python 2/3 cross compatibility. It also has the advantage of keeping Python 2.7 users on a time tested product. On the

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Seems pretty straightforward to me. Create a python 3 version as soon as possible and make it available, keep the python 2.7 version as default until the next major release after 4.0 (assuming around/after python 2.7 EOL), then switch default and leave continued support for 2.7 cqlsh up to the

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

All for using six and supporting both. Sorry, I read your initial email as wanting to drop support for 2 at the end of the year. > On Jun 1, 2018, at 1:01 PM, Jonathan Haddad wrote: > > And that's why I said supporting both with six is the right path > forward, later dropping support for 2.

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

If anything, riding on their coattails will mean we'll drop support a year or two later, after we see their experiences - which will be nicely in line with the Python upstream EOL date of 2020. (Of course, distro vendors will provide support after that, say till 2025.) So perhaps 2020 should be a

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

And that's why I said supporting both with six is the right path forward, later dropping support for 2. I'm not advocating we drop 2 support now, and I'm not asking for any sort of commitment. I didn't think adding support for 3 would be so controversial. On Fri, Jun 1, 2018 at 9:40 AM Jeremiah

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

The community of people doing python development and the community of people running Cassandra servers are not the same. I am not fine riding the coat tails of libraries used in python development. As others have stated we need to be following the lead of the OS vendors that people will be

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Both can work. I did a lot of the work on the port of the Python driver's object mapper (formerly cqlengine) to Python 3. It's reasonably straightforward if you use the six library. Both pandas and numpy are dropping support for Python 2 at the end of this year. I'm fine with riding on their

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Support for, but not the very script, right? Because, as gently pointed out by several realists here, Python 2 is far from dead and arguably still the majority usage. That's only just now beginning to change. I think it will be more than 2 years before people begin asking what Python 2 was.

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Supporting both as a next step is logical, removing support for 2 in the next year or two seems reasonable enough. Gotta rip the band aid off at some point. On Fri, Jun 1, 2018 at 2:34 AM Michael Burman wrote: > Hi, > > Deprecating in this context does not mean removing it or it being >

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Hi, Deprecating in this context does not mean removing it or it being replaced by 3 (RHEL 7.x will remain with Python 2.x as default). It refers to future versions (>7), but there are none at this point. It appears Ubuntu has deviated from Debian in this sense, but Debian has not changed yet

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

On 2018/06/01 07:40:04, Michael Burman wrote: > > IIRC, there's no major distribution yet that defaults to Python 3 (I > think Ubuntu & Debian are still defaulting to Python 2 also). This will > happen eventually (maybe), but not yet. Discarding Python 2 support > would mean more base-OS

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Hi, Should definitely be cross compatible with Python 2/3. Most of the systems (such as those running on RHEL7 or distros based on it like CentOS) are shipping with 2.7 only by default. And these systems are probably going to be used for a long time to run Cassandra. IIRC, there's no major

Planning to port cqlsh to Python 3 (CASSANDRA-10190)

I propose porting cqlsh and cqlshlib to Python 3. End-of-life for Python 2.7 is currently planned for 1 January 2020. We should prepare to port the tool to a version of Python that will be officially supported. I'm seeking input on three questions: -