root@t:~# cat $(which scapy)
    ++ which scapy
    + cat /usr/bin/scapy
    #!/usr/bin/python3
    # EASY-INSTALL-ENTRY-SCRIPT: 'scapy==2.5.0','console_scripts','scapy'
    import re
    import sys
    
    # for compatibility with easy_install; see #2198
    __requires__ = 'scapy==2.5.0'
    
    try:
        from importlib.metadata import distribution
    except ImportError:
        try:
            from importlib_metadata import distribution
        except ImportError:
            from pkg_resources import load_entry_point
    
    
    def importlib_load_entry_point(spec, group, name):
        dist_name, _, _ = spec.partition('==')
        matches = (
            entry_point
            for entry_point in distribution(dist_name).entry_points
            if entry_point.group == group and entry_point.name == name
        )
        return next(matches).load()
    
    
    globals().setdefault('load_entry_point', importlib_load_entry_point)
    
    
    if __name__ == '__main__':
        sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
        sys.exit(load_entry_point('scapy==2.5.0', 'console_scripts', 'scapy')())

I do understand your point, but that's pretty common for Python. Say you're using poetry (https://python-poetry.org/docs/pyproject/#scripts) or Uv (https://docs.astral.sh/uv/concepts/projects/config/#command-...) or setuptools (https://setuptools.pypa.io/en/latest/userguide/entry_point.h...) to define "scripts" for your package. Those tools will autogenerate a file like the one you posted here that basically import the package and then call a specific function inside it.

Almost all interesting Python scripts import another module, so it's really unusual to see all of a program's code in one file anyway. These autogenerated scripts just take it a step further.