Re^2: Proper handling of shebang line while performing local testing?


P is for Practical
	PerlMonks

Re^2: Proper handling of shebang line while performing local testing?

by nysus (Parson)

on Sep 05, 2018 at 07:01 UTC ( #1221734=note: print w/replies, xml )

Need Help??

in reply to Re: Proper handling of shebang line while performing local testing?
in thread Proper handling of shebang line while performing local testing?

Well, I've been googling around and it seems that the best practice for cpan modules is to use `/usr/bin/perl` and it will be replaced when the user installs the module. This is the best explanation I found on the matter: https://github.com/duncs/clusterssh/issues/45#issuecomment-153898849

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ Priest";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Re^2: Proper handling of shebang line while performing local testing?

Replies are listed 'Best First'.

Re^3: Proper handling of shebang line while performing local testing?
by Corion (Patriarch) on Sep 05, 2018 at 07:29 UTC

Maybe then you need to invoke your tests in a different way. I usually run single tests as

perl -Mlib -w t/01-api.t
[download]

... and the whole test suite with

make test
[download]

or, if I want to run the author tests as well, with:

make
prove -bl xt/ t/
[download]

Directly starting a test will get things confused because the kernel will invoke the Perl that is hardcoded in the first line instead of using the Perl that you (may) want.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom