Re: Use /usr/bin/env python3 in scripts?

For me merge script worked for python 2.7, but I got some trouble with the encoding issue (probably from contributor's name) so now I use the merge script with virtualenv & python 3.7.7. "python3" would be OK for me as well as it doesn't break virtualenv with python 3. On Sat, Jul 18, 2020 at

Re: Use /usr/bin/env python3 in scripts?

+1 I'm in favor of using python3 Cheers, Fokko Op vr 17 jul. 2020 om 19:49 schreef Sean Owen : > Yeah I figured it's a best practice, so I'll raise a PR unless > somebody tells me not to. This is about build scripts, not Pyspark > itself, and half the scripts already specify python3. > > On

Re: Use /usr/bin/env python3 in scripts?

Yeah I figured it's a best practice, so I'll raise a PR unless somebody tells me not to. This is about build scripts, not Pyspark itself, and half the scripts already specify python3. On Fri, Jul 17, 2020 at 12:36 PM Oli McCormack wrote: > > [Warning: not spark+python specific information] > >

Re: Use /usr/bin/env python3 in scripts?

[Warning: not spark+python specific information] It's recommended that you should explicitly call out python3 in a case like this (see PEP-0394 , and SO

Use /usr/bin/env python3 in scripts?

So, we are on Python 3 entirely now right? It might be just my local Mac env, but "/usr/bin/env python" uses Python 2 on my mac. Some scripts write "/usr/bin/env python3" now. Should that be the case in all scripts? Right now the merge script doesn't work for me b/c it was just updated to be