Felix Lechner <felix.lech...@lease-up.com> writes: >> Does "used" above refer to runtime usage? > > It refers to any use of the "python" package.
Since I am trying to understand what constitutes "use", could you please give examples? For instance does use here mean being an "input" to a package? Something more/less/else? > The native specifier means that the inputs have the same architecture > that Python is building something else on, rather than the architecture > it building that something else for. > > Inputs intended for the target architecture are runtime inputs. Given above, I would expect adding a variable to search-paths or native-search-paths to be functionally equivalent when not cross compiling. Do you agree with this, or am I mistaken in my conclusion? >> How does one determine which of native-search-paths or search-paths is >> appropriate in a given context? > > I'm not sure whether it makes a difference for interpreters. Perhaps > the distinction arises because some Python modules are compiled and > machine-dependent. At least for certain variables such as $SSL_CERT_DIR and $SSL_CERT_FILE they only have the desired effect when added to native-search-paths. When they were added to search-paths, I observed errors when accessing HTTPS resources (in a pure container with nss-certs included in the profile). When they were added to native-search-paths instead, the errors went away. -- Suhail
