That would be a (trivial) upstream change to the kernel as code is held there.
Unless it is still important to keep it also py2 executable - is it?
Per last commits on that file Stefan Raspl <email address hidden> should be best to decide where the upstream code should go to.
Even if it is py2 it should use the "env" sheband btw, see above pep link.
I agree that adding a dependency and pulling in python2 from the kernel seems very wrong.
Per https:/ /www.python. org/dev/ peps/pep- 0394/#recommend ation I think the right header would be
#!/usr/bin/env python3
That would be a (trivial) upstream change to the kernel as code is held there.
Unless it is still important to keep it also py2 executable - is it?
Per last commits on that file Stefan Raspl <email address hidden> should be best to decide where the upstream code should go to.
Even if it is py2 it should use the "env" sheband btw, see above pep link.