On Thu, Sep 1, 2022 at 12:20 PM <aster...@phreaknet.org> wrote: > On 9/1/2022 11:12 AM, Joshua C. Colp wrote: > > On Thu, Sep 1, 2022 at 12:10 PM <aster...@phreaknet.org > > <mailto:aster...@phreaknet.org>> wrote: > > > > > > I didn't notice any test suite code specifically calling python so > > this > > is purely a usage change, right? e.g. I should be running > > ./runInVenv.sh > > python3 runtests.py -l as opposed to ./runInVenv.sh python > > runtests.py -l > > It seems both may work but python3 would be the "more right" way > > to do > > it. So maybe the wiki page for that could be updated but a code > > change > > is not needed. > > > > > > runtests.py has python as its executable so you don't need to do > > "python runtests.py" assuming python3 is the default on the system. If > > not then you would need to, unless runtests.py was changed to have > > python3 as its executable. > > Ah, now I see what you mean. So that raises the question: shouldn't we > change #!/usr/bin/env python to #!/usr/bin/env python3? > If only python3 will work, I don't see the advantage of not specifying > so explicitly. >
That is what my original response was covering. -- Joshua C. Colp Asterisk Project Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
