lib_access_to_config_data

Problem

There should be a way to access protoprimer config data for reuse in other (entry) scripts.

Other scripts must always start as entry_script-s (see entry_script).

Using the data in entry script means protoprimer acts as a lib with API to provide that data.

The access to the config data depends on conf_leap starting from the path to proto_code.

Normally, detection of the reliable path to proto_code requires isolated_python which implies re-starting python with -I option.

Solution

The entry scripts can avoid python re-start by providing the path to proto_code.

The entry scripts are already running isolated_python.

protoprimer simply has to support running the DAG through the conf_leap without doing all things it does for boot_env.

See also

context_propagation provides the mechanism and function protoprimer.get_proto_kernel_abs_path to support this use case.