annotate requirements.txt @ 6802:b9853a3cc254

celery: simplify internal configuration and app creation We used celery.app.app_or_default() which creates a "global fallback app instance" which relies on the CELERY_LOADER environment variable to load the configuration. That worked but was messy. Instead, do something more like described in http://docs.celeryproject.org/en/3.1/userguide/application.html where the app is a celery.Celery() instance and configuration is loaded explicitly by its config_from_object method. Using config_from_object we don't need explicit invocation of import_default_modules and can take pass PylonsSettingsProxy directly, leaving PylonsLoader unused and removed. Modified by Mads Kiilerich.
author domruf <dominikruf@gmail.com>
date Sun, 11 Jun 2017 16:13:09 +0200
parents 941548131765
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
5741
941548131765 setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff changeset
1 # requirements.txt file for use as "pip install -r requirements.txt" as a
941548131765 setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff changeset
2 # readthedocs compatible alternative to "pip install -e ." which is a working
941548131765 setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff changeset
3 # alternative to "setup.py develop" which doesn't work with Mercurial 3.7
941548131765 setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff changeset
4 .