Path: csiph.com!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: aotto1968 Newsgroups: comp.lang.python Subject: Re: it's a shame... python error over error Date: Fri, 13 Dec 2024 11:49:11 +0100 Organization: A noiseless patient Spider Lines: 21 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Fri, 13 Dec 2024 11:49:11 +0100 (CET) Injection-Info: dont-email.me; posting-host="23d41c05675a617b44c2c1d1b1a1ed81"; logging-data="3536952"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18v7U/lhRHtN9olMEsQi/j5esIJtk/UUko=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:15Wr4hNXMjD4ZyZwPsyk2gIoYc8= In-Reply-To: Content-Language: en-US Xref: csiph.com comp.lang.python:197055 On 13.12.24 11:44, aotto1968 wrote: > On 13.12.24 11:36, aotto1968 wrote: >> it's a shame... >> 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. >> > > 1. The build is done with my user and the installation is done as root. > 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. even the `sudo -E make install` with "-E, --preserve-env" does help.