Primary use case¶
You can use standard /usr/bin/env command inside shebang to provide environment variables to
change the behavior of the script:
#!/usr/bin/env -S ENV_VAR_1=value_1 ENV_VAR_2=value_2 python
It is especially useful in the case of minimal env_layout
when the client code is kept clean of any extra config files.
This is the only way to tell proto_code a non-default path to the file with leap_primer conf
(see conf_leap).
However, the approach is limited by the maximum size of the shebang line (practically, it is only 127 chars).
TODO: implement and update this doc with example Specify the env var