Liste des Groupes | Revenir à cl python |
On 13.12.24 11:36, aotto1968 wrote:even the `sudo -E make install` with "-E, --preserve-env" does help.it's a shame...1. The build is done with my user and the installation is done as root.
almost every tool I touch that uses "python" in some way has some configuration error because apparently a __private__ python installation __isn't__ properly "understood".
>
-> I think after ~30 years *python* should be able to handle a shared-library proper __or__ switch to a *static-build* by default.
>
-> example here is the "mono-build" with the following installation.
>
2. The setup proper find *my* python3 because my PATH etc is setup well.
3. root is an other environment and root does *not* have my environment.
4. root uses *my* python3 without *my* environment and is *not* able to find
*my* libpython3.12d.so.1.0
5. obviously the *python3* is *not* able to create the right environment from
the installation directory of the *python3* executable.
Les messages affichés proviennent d'usenet.