Re: prevent AppConfig.ready() from running twice

Thanks so much, y'all! Very helpful!

On Sunday, June 24, 2018 at 3:47:48 AM UTC-4, Mike Dewhirst wrote:

On 23/06/2018 6:17 PM, Melvyn Sopacua wrote:
> On zaterdag 23 juni 2018 02:01:06 CEST Mike Dewhirst wrote:
>
>> Is there a python singleton pattern which might work?
> No, cause the startup is done in 2 different processes which do not share
> state. So both processes will have a "new singleton".
> This is why you need an IPC mechanism, such as file locks or shared memory.

OK. That's very clear. Thank you Melvyn.

Cheers

Mike

>   In
> the case of one-off launchers, it's usually easier to implement the
> restrictions on the client side (the program being launched). Long running
> launchers (like inetd, systemd) can prevent double launch in other ways as
> they can keep their own state.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5bee9c83-aec8-4a72-a9e6-1196bb989df1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.