Is it different for Java? How do you get Java 11 on RHEL 7? On Mon, Mar 11, 2024 at 5:58 PM David Capwell <dcapw...@apple.com> wrote:
> Is it not possible to install and run python 3.8 on RHEL 7? > > > You have a few options, none really good. > > 1) build from source > 2) a RPM from outside of RHEL; this means you don’t have support and must > trust a different third party (not managed by python or RedHat) > 3) you use SCL which means every time you want to touch CQLSH you have to > remember to enable it (as its per-bash session) > > These 3 options don’t really work for most deployments > > > On Mar 11, 2024, at 1:12 PM, Brad <bscho...@gmail.com> wrote: > > RHEL 7 will reach the end of maintenance on June 30th, 2024 (extended > lifecycle support is an option). > > Is it not possible to install and run python 3.8 on RHEL 7? I assume that > would be necessary to run Java 11 on RHEL 7 with Cassandra 5.0. It would > be a burden for contributors to test with an obsolete version of python -- > you can't 'brew install python@3.6' for example. > > % brew install python@3.6 > Warning: No available formula with the name "python@3.6" > > % brew install python@3.7 > Error: python@3.7 has been disabled because it is deprecated upstream! > > > On Mon, Mar 11, 2024 at 3:38 PM Caleb Rackliffe <calebrackli...@gmail.com> > wrote: > >> I can try this out on trunk. Will report back... >> >> On Mon, Mar 11, 2024 at 2:23 PM J. D. Jordan <jeremiah.jor...@gmail.com> >> wrote: >> >>> The Python driver dropped official support for older EOL Python versions >>> because they are EOL and no longer tested by the newer driver CI. I don’t >>> think there are actually any changes yet that it won’t work in 3.6 still? >>> Maybe someone with Python 3.6 installed can change the if and see? I think >>> we have some cqlsh tests in dtest? As long as we as a project run those on >>> RHEL 7, I would be comfortable with adding that back to being supported. >>> Though maybe just in the rpm package? >>> >>> -Jeremiah >>> >>> On Mar 11, 2024, at 1:33 PM, Josh McKenzie <jmcken...@apache.org> wrote: >>> >>> >>> Looks like we bumped from 3.6 requirement to 3.7 in CASSANDRA-18960 >>> <https://issues.apache.org/jira/browse/CASSANDRA-18960> as well - >>> similar thing. Vector support in python, though that patch took it from >>> "return a simple blob" to "return something the python driver knows about, >>> but apparently not variable types so we'll need to upgrade again." >>> >>> The version of the Python driver that is used by cqlsh (3.25.0) doesn't >>> entirely support the new vector data type introduced by CASSANDRA-18504 >>> <https://issues.apache.org/jira/browse/CASSANDRA-18504>. While we can >>> perfectly write data, read vectors are presented as blobs: >>> >>> >>> As far as I can tell, support for vector types in cqlsh is the sole >>> reason we've bumped to 3.7 and 3.8 to support that python driver. That >>> correct Andres / Brandon? >>> >>> On Mon, Mar 11, 2024, at 1:22 PM, Caleb Rackliffe wrote: >>> >>> 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. >>> > $ >>> > >>> > >>> >>> >>> >
