On 2022-07-17 17:42:34, Dima Pasechnik wrote: > On Sun, Jul 17, 2022 at 5:08 PM Thierry <sage-googlesu...@lma.metelu.net> > wrote: > > while running a patchbot client, i see a lot of unfinished processes > > whose command is "python3 /home/sagemath/sage/src/bin/sage-ipython -i" > > at various dates, indicating that something is not killed properly. The > > phenomenon is not new. Any hint on how to fix that ? > > this might have gotten broken in https://trac.sagemath.org/ticket/8784 > > Namely, in this chunk: > > ... > > Maybe the author could say more. >
I hope not. Before that ticket, the user was supposed to call quit_sage() to e.g. properly free memory and terminate lingering pexpect processes before leaving sage. When using sage interactively, ipython made the call. But when using sage as a library, approximately no one knew to call quit_sage() at the end of their code. To address that, the ticket took everything that was in quit_sage() and made it happen automatically when the process exits, so the user is no longer responsible for calling quit_sage(), regardless of how sage is being used. As a result, neither ipython nor the user should need to call quit_sage(). But who knows. If that change caused it, it caused it. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/Ytf5iN4SCAdZOJrN%40stitch.
