The vector issues itself was a simple error message change: https://github.com/datastax/python-driver/commit/e90c0f5d71f4cac94ed80ed72c8789c0818e11d0
Was there something else in 3.29.0 that actually necessitated the move to a floor of Python 3.8? Do we generally change runtime requirements in minor releases for the driver? On Mon, Mar 11, 2024 at 12:12 PM Brandon Williams <dri...@gmail.com> wrote: > Given that 3.6 has been EOL for 2+ years[1], I don't think it makes > sense to add support for it back. > > Kind Regards, > Brandon > > [1] https://devguide.python.org/versions/ > > On Mon, Mar 11, 2024 at 12:08 PM David Capwell <dcapw...@apple.com> wrote: > > > > Originally we had planned to support RHEL 7 but in testing 5.0 we found > out that cqlsh no longer works on RHEL 7[1]. This was changed in > CASSANDRA-19245 which upgraded python-driver from 3.28.0 to 3.29.0. For > some reason this minor version upgrade also dropped support for python 3.6 > which is the supported python version on RHEL 7. > > > > We wanted to bring this to the attention of the community to figure out > next steps; do we wish to say that RHEL 7 is no longer supported (making > upgrades tied to OS upgrades, which can be very hard for users), or do we > want to add python 3.6 support back to python-driver? > > > > > > 1: the error seen by users is > > $ cqlsh > > Warning: unsupported version of Python, required 3.8-3.11 but found 3.6 > Warning: unsupported version of Python, required 3.8-3.11 but found 2.7 > > No appropriate Python interpreter found. > > $ > > > > >
