Sigh... So much for trying to have it work for either python3 or python2. The doc you referenced does say: "If the executables provide the same functionality independent of whether they are run on top of Python 2 or Python 3, then only the Python 3 version of the executable should be packaged." However, since 2.7 runs so much faster, and 2.7 is still the default for the near future, I agree we should stay with 2.7. I'll back out that tweak and create a new patch. Thanks Kris Davis -----Original Message----- From: Sitsofe Wheeler [mailto:sitsofe@xxxxxxxxx] Sent: Wednesday, February 21, 2018 11:24 AM To: Kris Davis <Kris.Davis@xxxxxxx> Cc: Vincent Fu <vincentfu@xxxxxxxxx>; Vincent Fu <Vincent.Fu@xxxxxxx>; fio@xxxxxxxxxxxxxxx; Jens Axboe <axboe@xxxxxxxxx> Subject: Re: fiologparser_hist.py script patch and enhancements? Hi, Alas no. It's less of a case of "is the Python version at least 2.7" and more a case of "not all platforms have a "python2" link (see macOS) / distros are banning interpreters lines that mention just "python" (see https://fedoraproject.org/wiki/Packaging:Python#Multiple_Python_Runtimes ). On 21 February 2018 at 17:00, Kris Davis <Kris.Davis@xxxxxxx> wrote: > I had changed the interpreter to just be "python" rather than "python2.7", and added a check to ensure that the python version was at least 2.7. This allows it to use whatever version (2.7 or above) that has been associated with "python" (usually 2.7+ in recent linux os's). What I've see (unless a virtualenv is used), python 3+ has a symlink set to python3. > The point is, if the interpreter is set to python2.7, the user is generally "forced" to use 2.7, unless all command lines are prepended with the python?? > > Does that address your concern? -- Sitsofe | http://sucs.org/~sits/ ��.n��������+%������w��{.n�������^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
