[Python-Dev] startup time repeated? why not daemon

[Oleg Broytman]

On Thu, Jul 20, 2017 at 01:53:52PM -0400, "Jim J. Jewett" <jimjjewett at gmail.com> wrote:
> I agree that startup time is a problem, but I wonder if some of the pain
> could be mitigated by using a persistent process.
> 
> For example, in
> https://mail.python.org/pipermail/python-dev/2017-July/148664.html Ben Hoyt
> mentions that the Google Cloud SDK (CLI) team has found it "especially
> problematic for shell tab completion helpers, because every time you press
> tab the shell has to load your Python program"
> 
> Decades ago, I learned to set my editor to vi instead of emacs for similar
> reasons -- but there was also an emacsclient option that simply opened a
> new window from an already running emacs process.  tab completion seems
> like the exactly the sort of thing that should be sent to an existing
> process instead of creating a new one.
> 
> Is it too hard to create a daemon server?
> Is the communication and context switch slower than a new startup?
> Is the pattern just not well-enough advertised?

   Just yesterday there was a link to such a daemon that caches pyGTK.
Eons ago I'd been using ReadyExec: http://readyexec.sourceforge.net/

> -jJ

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.