Gian Piero Carrubba wrote: > The rationale behind this statement is that a perl script shipped > within Debian has its dependencies fulfilled via the package > manager. This cannot be guaranteed if the perl environment > interpreting it is not itself shipped via Debian. > When using `#!/usr/bin/env perl', the script is interpreted by the > first perl binary found in the $PATH of the user, so there's no > guarantee this is the perl binary shipped by Debian. Wouldn't this argument apply equally well to #!/usr/bin/env python, which is quite commonly used? -- see shy jo
Attachment:
signature.asc
Description: Digital signature