[asksol]

Thanks for the comments! Feedback on documentation is always welcome as it's hard to step inside the state of someone starting to use the project. I wish people would speak out more as I'm sure there are many more issues with the docs. The best way to get this solved is to open an issue at http://github.com/celery/celery/issues, you can even make suggestions.

1) How does it differ from startproject? 2) That's how you tell Celery to use your Django project settings as a source of configuration. Did you read the 'First steps with Celery' guide first? 3) The old Python import behavior is very limiting, and starting from Python 3 absolute import is the default. We believe everyone should start using it by importing it in all modules, but you don't have to if you don't want to, just give it another name. 4) The Django result backend is a stable component, the Django ORM message transport is not, so we won't tell you how to use it in the introduction because we don't want you to. You can find the instructions here: http://docs.celeryproject.org/en/latest/getting-started/brok... 5) Everything is supported out of the box except for storing results using the Django ORM (there's built-in sqlalchemy result backend that can also be used, but it's not compatible with the Django backend as the data is stored in a slightly different way: https://github.com/celery/celery/issues/183)