Oct-01-2019, 03:20 PM
(This post was last modified: Oct-01-2019, 03:37 PM by Suryavarman.)
I have build the latest release of python3 on a Mageia7 system.
Here the configuration command line:
And if I call pip3 like that:
All this command lines have the same result.
An output example:
(Please don't ask me to use a venv, virtualenv or anaconda or wathever... I hate the hasardous behaviour of this things.
)
Response: don't build python with the shared option.
It's works. I don't khow why.
Here the configuration command line:
./configure --prefix=${PY_PATH} --enable-shared
And if I call pip3 like that:
${PY_PATH}/bin/pip3 …
${PY_PATH}/bin/python3 pip3 …
${PY_PATH}/bin/python3 ${VENV_PATH}/bin/pip3 …
${PY_PATH}/bin/python3.7 ${VENV_PATH}/bin/pip3.7 …
${PY_PATH}/bin/python3.7m ${VENV_PATH}/bin/pip3.7 …
All this command lines have the same result.
An output example:
Output:Requirement already satisfied, skipping upgrade: apipkg>=1.4 in /usr/local/lib/python3.7/site-packages (from execnet>=1.1->pytest-xdist) (1.5)
Or :Error:ERROR: Could not install packages due to an EnvironmentError: [Errno 13] Permission non accordée: '/usr/local/bin/f2py'
Consider using the `--user` option or check the permissions.
Why ${PY_PATH}/bin/python3 ${VENV_PATH}/bin/pip3
call the pip3 system from /usr/bin?(Please don't ask me to use a venv, virtualenv or anaconda or wathever... I hate the hasardous behaviour of this things.

Response: don't build python with the shared option.
It's works. I don't khow why.