For anyone that finds this thread, here is what I've found...
The system installed version of supervisor, installed via apt, presently is 3.3.1. This is ubuntu 18.04.
What is important to note is that the first line in /usr/bin/supervisord
is #!/usr/bin/python
.
This is the python 2.7 version on my system.
Looking at https://github.com/Supervisor/supervisor/blob/3.3.1/supervisor/supervisord.py
, it has #!/usr/bin/env python
as the first line. This could possibly call a python3 version if it is set in the path whereby python implies python3.
However...
It appears that the install produces a stub program in /usr/bin/supervisord
which then calls an entry point, thereby running the supervisord.py
code.
So no matter how you set your path, how python may be set to calling a python3 program...
Its not going to get around the hard-coded #!/usr/bin/python
call in /usr/bin/supervisord
.
One alternative is setting up alternatives
which results in /usr/bin/python
being python3.
So you need to do some tracking down of how python2 and python3 are deployed on your system.