@resam said in pip won't install dsf-python-3.5.1rc1:
@achrn not sure such a hard stance is needed here. Its perfectly fine to override this behaviour if you know what you are doing.
It's the 'if you know what you are doing' part that's the problem. I don't know anything about this change to pip or the virtual environment system, and the which of the four different ways that message might be telling me to proceed is not obvious to me.
I'm not trying to be hardline, I'm just trying to get the software installed.
@Falcounet said in pip won't install dsf-python-3.5.1rc1:
Yes it will work. The virtual environment is for python only. It will still connect to DSF using the IPC API.
For dsf plugins to work, you need to have dsf-python installed for dsf user.
I'm unclear whether installing it for (as?) a user and installing it in a virtual environment are two different options, but notwithstanding that:
I'm not sure how to install as dsf, given that the account is nologin. There is no password for dsf. sudo su dsf gives me This account is currently not available. Should I just set dsf to allow login and then login as that user and do the pip3 command? I'm a little nervous that doing that might upset something else that uses the dsf user.
If it's in an environment, I note the web page linked says "activate that environment before running any of your Python code", so that presumably requires DSF to do that step if it's a plugin? Is there a need to do anything to tell DSF of the virtual environment (or indeed which virtual environment) to run a plugin in?
Given these questions, I think I'll try the --break-system-packages option first,