I agree with Ken, that this a Celery issue, not a Django one. But while we're here, as far as I know Celery still runs fine on windows. It is not officially supported, and the default pool no longer works, but if you run celery with --pool=solo (in development) or --pool=gevent (in production) it should run without problems. You might run into issues, as the Celery developers highlight, but I would expect that for a relatively normal use case it might be fine.
There is also the upcoming background worker support to consider if it suits your use case: https://www.djangoproject.com/weblog/2024/may/29/django-enhancement-proposal-14-background-workers/ Cory On Thu, Aug 22, 2024 at 4:36 PM 'Ken Whitesell' via Django developers (Contributions to Django itself) <django-developers@googlegroups.com> wrote: > I think you're misinterpreting what you're reading from your search > results. > > This is a Celery issue, not a Django issue. > > Quoting from the Celery docs at > https://docs.celeryq.dev/en/stable/faq.html#does-celery-support-windows > > ----- > Does Celery support Windows? > <https://docs.celeryq.dev/en/stable/faq.html#id59> > <https://docs.celeryq.dev/en/stable/faq.html#does-celery-support-windows> > > *Answer*: No. > > Since Celery 4.x, Windows is no longer supported due to lack of resources. > > But it may still work and we are happy to accept patches. > > ----- > > On 8/21/2024 9:03 AM, Muhammad Shariq Shafiq wrote: > > Hello Dear Django Team > > Last month, I tried to do some task of django which primarily based on > scheduling of accessibility with time and role based authnetications > > I used celery for that scheduling but failed and for 2 days i tried for it > by changing my code logic and urls but all in vain > > Then i read from google that django has no longer support of celery for > windows user. Which is not a good for developers > > We have to make things easy for developers to captivate the ideas into > reality without any limitatoons. > > My suggestion and request to you to make celery working again on windows > so that the developers can use it effeciently and produces more productivity > > Regards > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/08095574-14fc-425e-b36a-59c095f0dc07n%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/08095574-14fc-425e-b36a-59c095f0dc07n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/4b4bbca5-5023-4029-b043-5fc577cb7b9d%40comcast.net > <https://groups.google.com/d/msgid/django-developers/4b4bbca5-5023-4029-b043-5fc577cb7b9d%40comcast.net?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALojRn_QFJxWVBgaC45t_Wq016eqd2P2yQqFsBh0niPbA4hAgA%40mail.gmail.com.
