-
Notifications
You must be signed in to change notification settings - Fork 457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decorator @task_with_respect_to_language for using tasks with respect of current site's languages #21
Comments
It is certainly useful, but the implementation is maybe a little to specific. It would be much more useful like this:
and then I think it would be much better as a contextmanager:
|
Thanks for recommendations. I modify code with respect to them. And add small test for 'with' statement
|
Thanks! Sorry for the late reply, seems I missed this for some time. Lots of stuff going on at the same time :( The documentation seems to be out of date, could you update that, and also document the purpose of Thanks in advance! |
I updated patch and published it here http://dpaste.com/276957/ |
Shit, I closed it by mistake... Can you reopen it or... maybe apply my patch ? :-) |
It doesn't seem like I can reopen it :( But could you fork the project and make a pull request instead? That is a lot easier to work with, and for me to merge it and maintain author info. |
I see a little problem with it. Now I use your branch "release20-maint" for working with r13315 revision of Django. Can you suggest to me, what branch is better to patch. I can not use "master" and in this way I prefer "release20-maint". But may be it's not good for you and purposes of creating this branch. What do you think about it? |
You can work on either one; release21-maint or master. I will do the merging necessary afterwards :) |
I have done this - https://github.com/ask/django-celery/pull/31 |
What do you think about add this to repo?
Created by recommendations from here http://celeryq.org/docs/django-celery/faq.html#generating-a-template-in-a-task-doesn-t-seem-to-respect-my-i18n-settings
The text was updated successfully, but these errors were encountered: