I suppose functionally there may be little difference, but having an explicit "runner" would allow two things:
1. the runner and stdlib for it could be in a compress format itself since it doesn't need to provide any utility for editing or navigating human readable modules. and so lighter 2. it would handle "venv"ing and creating desktop shortcuts etc that would just start the python app in the engine. The reason I mention this here, is because others have said that including functionality to deal with this sort of thing for _all_ OS would be heavy, where as here it could be more lightweight and even not part of the standard python interpreter, just the runner. Also on systems with python already installed it could be told to use the existing python install, if that was desired. _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/GEYD5SVEO3YV2NNSLNLNQPAYAHZJOCU6/ Code of Conduct: http://python.org/psf/codeofconduct/
