Thanks. I added it to /etc/profile and reloaded bash but it doesn't work. The packages I installed with -t show up via pip3 list. However, they still don't run via the command line with "mnamer" or "python3 mnamer" python3: can't open file 'mnamer': [Errno 2] No such file or directory
I think I am missing something pretty basic here but not sure what. When you say copying binaries do I need to do that manually?
Just to be clear, if you are using bash (and not ash) and not using a --login option, you most likely need to have the PYTHONPATH in .bashrc or similar.
Also, to use mnamer directly, there needs to be the entrypoint in your PATH (which is the part where I wasn't sure about pip3 behaviour on -t as I haven't used it before)
Can you run a couple of commands just to give us a feel for your setup?
pip3 show mnamer
find / -name mnamer
The first one to see that PYTHONPATH is in fact set. The second one to check what pip3 did with the package and the third one to see if we can find the mnamer entrypoint.
For the last one, /mnt/sda1/config/ exists because I tried installing it to a non-hidden directory but it didn't work so I went back to the .config directory. I uninstalled the packages with pip3 but it didn't seem to remove those entry points.
So, for you to call directly mnamer, it needs to be in your PATH.
You can first try directly with the full path to see if it works.
Does that work if you run it?
Then the next thing is that python complained it couldn't find mnamer but that's because it was looking for that file locally when you run the command.
To see if it's in your PYTHONPATH, you can try the following:
>>> from mnamer.__main__ import main
mnamer [preferences] [directives] target [targets ...]
But I'd say, you should just focus on being able to run the mnamer script from the bin/ directory (and forget about the python3 way, unless you want to extend the package with your own script, in that case, use the imports the way I did in that last example)