Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
What does [...] or -*- means in -*-_DB_SHORT_LIVED_SESSIONS #5819
Milestone
Comments
|
I have to say, I honestly don't know what this setting is or what it does. |
|
you should use the lowercase database_short_lived_sessions instead |
Does that apply for Django settings as well? |
|
for celery related yes |
|
-*- encoding declaration |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
for similar or identical bug reports.
for existing proposed fixes.
to find out if the bug was already fixed in the master branch.
(If there are none, check this box anyway).
Related Issues and Possible Duplicates
Related Issues
Possible Duplicates
Description
The documentation https://docs.celeryproject.org/en/latest/history/whatsnew-4.0.html#latentcall-django-admonition is inconsistent when it comes to -*-_DB_SHORT_LIVED_SESSIONS.
I can't find guidance about what does -*- represents and what should be the final name on that setting.
I have tried CELERY_DEFAULT_DB_SHORT_LIVED_SESSIONS but the 2006 MySQL problem is supposed to fix continues to happen so I assume the setting is wrong. We need a clearer doc on how to use that setting.
Suggestions
Give an example on how the configuration should look in a Django file and explain what -*- represents. Also, I have seen it as [...] in other places so it should be consistent unless it's meant to be intentionally different.