-----Original Message----- From: Python-Dev [mailto:python-dev-bounces+tritium- firstname.lastname@example.org] On Behalf Of Paul Moore Sent: Saturday, July 22, 2017 4:14 AM To: David Mertz email@example.com Cc: Barry Warsaw firstname.lastname@example.org; Python-Dev <python- email@example.com> Subject: Re: [Python-Dev] Python startup time
It's a bit of a chicken and egg problem - Windows users avoid excessive command line program invocation because startup time is high, so no-one optimises startup time because Windows users don't use short-lived command line programs. But I'm seeing a trend away from that - more and more Windows tools these days seem to be comfortable spawning subprocesses. I don't know what prompted that trend.
The programs I see that are comfortable spawning processes willy-nilly on windows are mostly .net, which has a lot of the runtime assemblies cached by the OS in the GAC - if you are spawning a second processes of yourself, or something that uses the same libraries as you, the compile step on those can be skipped. Unless you are talking about python/non-.NET programs, in which case, I have no answer.
Paul _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/tritium- list%40sdamon.com