Re: Python (was Re: I did not inhale)

On Thu, 22 Aug 2024 13:58:54 -0000 (UTC)
Lew Pitcher <lew.pitcher@digitalfreehold.ca> boringly babbled:

Please forgive my interruption, but something in Muttley's comment needs
some clarification....

For a properly designed language a container shouldn't be required. Using
a container to prevent library hell is like seeing a mess on your floor but
instead of clearing the mess you sweep it into seperate piles depending on
the type of rubbish. With C/C++ you can set LD_LIBRARY_PATH

>
1) The ability to alter the loader's library search path isn't a C/C++ feature,
>
  but, instead, is a feature of the loader, and is applicable to /any/ binary
  that uses "shared objects" ("DLL"s to those who came from a Windows
environment).

Sure, but the vast majority of *nix binaries will have been written in C or C++.

  Depending on the Unix system, the environment variable can be called:
    LD_LIBRARY_PATH, or

Works on Linux, BSD and Solaris so cover most bases.

    LIBPATH, or
    SHLIB_PATH, and
  there may be other names that I don't know of.

Point is the path to load dynamic libraries from can be switched very
easily and requires no changes to the system (other than installing the
alternate libs in the first place).