[Gluster-devel] Python3 build process

Shyam Ranganathan srangana at redhat.com
Fri Sep 28 12:57:45 UTC 2018

On 09/28/2018 12:36 AM, Kotresh Hiremath Ravishankar wrote:
>     > - All regression hosts are currently py2 and so if we do not run
>     the py
>     > shebang correction during configure (as we do not build and test from
>     > RPMS), we would be running with incorrect py3 shebangs (although this
>     > seems to work, see [2]. @kotresh can we understand why?)
>     Is it because we don't test any of the python in the regression tests?
> Geo-replication do have regression tests but not sure about glusterfind,
> events.
>     Or because when we do, we invoke python scripts with `python foo.py` or
>     `$PYTHON foo.py` everywhere? The shebangs are ignored when scripts are
>     invoked this way.
> The reason why geo-rep is passing is for the same reason mentioned. Geo-rep
> python file is invoked from a c program always prefixing it with python
> as follows.
> python = getenv("PYTHON");
>     if (!python)
>         python = PYTHON;
>     nargv[j++] = python;
>     nargv[j++] = GSYNCD_PREFIX "/python/syncdaemon/" GSYNCD_PY;

Thank you, makes sense now.

More information about the Gluster-devel mailing list