Re: when and why did python(-minimal) become essential?
> That sounds good, but wouldn't it be even better to have a symlink
> /usr/bin/debpython-minimal or so, pointing to the interpreter? Then one
> could still replace the interpreter by something else (by putting it
> into /usr/local/bin), for example in order to debug a particularly weird
> problem in a config script?
Or python-minimal could just provide /usr/bin/python-minimal. Then
programs with minimal requirements would have #!/usr/bin/python-minimal
and their packages would Depend on python-minimal, whereas normal python
programs would have #!/usr/bin/python and would Depend on python.
Behind the scenes /usr/bin/python would be a symlink to
python-minimal but users wouldn't have to know this. The interpreter
could even be modified so that it allows only modules from the minimal
set to be imported, when run as /usr/bin/python-minimal.
Thus if upstream's concern is that users not have a stripped down python,
then Debian provides a stripped down "python-minimal" instead.