Celery fails when installed on Windows 7

Issue #119 resolved
Ed McDonagh
created an issue

If the openrem folder is on the Python path in a Windows install, Celery will start but all the workers will be immediately killed as they are created.

The issue is described here: https://groups.google.com/forum/?pli=1#!topic/celery-users/i4sxrsfFStc

I have filed a bug report against Celery here: https://github.com/celery/celery/issues/2247

Comments (10)

  1. Ed McDonagh reporter

    Options are:

    1. Change the name of the Django project, ie the PyPI package will still be called openrem, but the Django project within would be called something else, such as openremproject.
    2. Wait for the Celery bug report to be investigated, and hopefully patched to fix it.

    Option 1 might be a headache depending on how much it changes the database tables. Otherwise it will be a case of changing import arguments and all the documentation.

    Option 2 might not ever happen. If it does, it might be possible to add some instructions to the documentation for Windows users to manually apply the patch. Otherwise this version of OpenREM would not be available to them until a later version of Celery was released, which we have no control over.

  2. Ed McDonagh reporter

    OpenREM user @David Platten has not reported having this difficulty with his OpenREM 0.4.3b3 install on Windows server 2008. I have tried it on Windows 7 Professional 64 bit as installed by HP on a laptop, and also the same OS version installed in a Virtual Machine.

  3. Ed McDonagh reporter

    Making changes in docs from openrem --> openremproject for the inner Django project folder. Addeded comment to restart Celery in the generic release upgrade notes. Haven't tackled upgrades yet. Refs #119.

    → <<cset c01ca070926a>>

  4. Log in to comment