it's a shame... python error over error
aotto1968
aotto1968 at t-online.de
Thu Dec 26 02:42:08 EST 2024
On 26.12.24 04:55, Michael Torrie wrote:
> On 12/25/24 3:55 PM, Chris Angelico via Python-list wrote:
>> On Thu, 26 Dec 2024 at 09:27, aotto1968 via Python-list
>> <python-list at python.org> wrote:
>>> It is not only an *usage* error it is also an *security* error because:
>>>
>>> 1) "cnf" is using OS python
>>> 2) os "root" python
>>> 3) using **my** local non-root library
>
> I think he means the cnf is using the "root" OS python in /usr/bin, but
> /usr/bin/python3 is trying to import his local build of sqlite3, which
> cause it to fail. I assume he would like cnf to not try to import his
> local sqlite3, and instead use the normal system one. If this is the
> case, then somehow his local, non-root sqlite3 library is being picked
> up by the system version of python.
>
> Aotto might want to run the "env" command and see if there are any
> search paths that have to do with Python. I can see how this could be a
> security issue. If you can figure out what's happening you might want to
> open a ticket with the OpenSUSE developers. This is Python related, but
> it's not necessarily python's fault per se.
Yes I using with *my* user *my* environment but never touch the *root*
environment at all.
the *root* python try to use *my* sqlite3 because *my* environment
fit to *my* needs.
/* just a reminder */
sqlite3 have a "special" (worse) setup that a change to the configuration
also change the "api" ( a sqlite_function disappear or arrive ).
If a tool like python using an extension that is linked to sqlite3 that extension
will likely FAIL is I get an OTHER sqlite3 which is NOT the one the extension
was build with.
More information about the Python-list
mailing list