Not setting python major version in QS scripts

[Paul-Adrien Cordonnier <pa...@adaltas.com>]

Hi all,

We are building and distributing Phoenix in a stack derived from Apache 
Hadoop and Hbase.

We are having a very minor issue with the QueryServer and I'm curious of 
your opinions.

The provided `queryserver.py` script uses "#!/usr/bin/env python". 
However this does not resolve on our RHEL8 as Red Hat declares that the 
OS should not be opinionated on using python2 or 3 as the "default 
python major version".

The issue is easily fixable on the OS by setting "python" to "python3" 
(but creates some controversy !).

I was curious if there are plans to drop python2 support in these 
scripts and just sets the shebang to python3.  We might do that in our 
fork but we try to deviate as little as possible from Apache Upstream. 
Again this is a very minor issue.

Thanks

Regards

PA Cordonnier

Re: Not setting python major version in QS scripts

[Istvan Toth <st...@cloudera.com>]

Hi.

We have no plans to drop python2 support in the foreseeable future, unless
it becomes too unwieldy to keep supporting it.

You can set the default python version in RHEL easily, and as I have not
seen this error on our RHEL 8 systems, this seems to be picked  up by
/usr/bin/env:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/assembly_configuring-the-unversioned-python_configuring-basic-system-settings

As Phoenix works with 2 and 3 as well, it doesn't matter what you set it
to, as long the OS can find any python.

regards
Istvan

On Tue, Jun 27, 2023 at 5:18 PM Paul-Adrien Cordonnier <
pauladrien@adaltas.com> wrote:

> Hi all,
>
> We are building and distributing Phoenix in a stack derived from Apache
> Hadoop and Hbase.
>
> We are having a very minor issue with the QueryServer and I'm curious of
> your opinions.
>
> The provided `queryserver.py` script uses "#!/usr/bin/env python". However
> this does not resolve on our RHEL8 as Red Hat declares that the OS should
> not be opinionated on using python2 or 3 as the "default python major
> version".
>
> The issue is easily fixable on the OS by setting "python" to "python3"
> (but creates some controversy !).
>
> I was curious if there are plans to drop python2 support in these scripts
> and just sets the shebang to python3.  We might do that in our fork but we
> try to deviate as little as possible from Apache Upstream. Again this is a
> very minor issue.
>
> Thanks
>
> Regards
>
> PA Cordonnier
>
>

-- 
*István Tóth* | Sr. Staff Software Engineer
*Email*: stoty@cloudera.com
cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
------------------------------
------------------------------