For what it's worth I feel your pain and I think it's impossible to win until there's only one version of Python actively left. My hope is by making it consistent across all the fio scripts everyone will be the same jam and will at least be able to do a find/replace. Perhaps someone should suggest a PEP which is an interpreter line that is just a line like preferredpython[2,3] and everyone is just expected to run a small conversion tool before starting to use it. Said conversion tool can rewrite the line to be env based, absolute, prefer python 3 to python 2 if when it's a Sunday and the weather's good... On 21 February 2018 at 17:45, Kris Davis <Kris.Davis@xxxxxxx> wrote: > 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. -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
