On Wed, Jun 02, 2021 at 10:50:11AM +0200, Jan Engelhardt wrote:
On Wednesday 2021-06-02 10:45, Ben Greiner wrote:
Am 02.06.21 um 10:26 schrieb Jan Engelhardt:
python3 would hardly exec /usr/bin/python (v2). They're still sane.
Many ignorant python scripts
Ignorant scripts are one thing. Ignorant node runtimes is another level.
Well, I kind of detect a bias? Here's a naive python example, f133:~ # cat worker.py #!/usr/bin/python3 import platform print(platform.python_version()) f133:~ # cat daemon.py #!/usr/bin/python3 import subprocess subprocess.Popen(['./worker.py']).wait() f133:~ # python3. python3.6 python3.6m python3.8 python3.9 f133:~ # python3.6 ./daemon.py 3.8.10 f133:~ # python3.6 ./worker.py 3.6.13 So, with node, if you did this experiment, and you started it with node10, you would get node10 in the worker irrespective what /usr/bin/node points to. Basically, once we allow multiple interpreters to be co-installed, they actually should run as expected. No? Saying the problem is "out of scope" tells me that something is abused for purposes that were not intended (looking at update-alternatives here). Anyway, this is an example of why pure symlinks are bad and actually result in confusion at runtime. - Adam