Allow using django CMS with custom admin site #3354
Conversation
| @@ -3,6 +3,8 @@ | |||
| from datetime import datetime | |||
| from itertools import chain | |||
| import re | |||
| from classytags.values import StringValue | |||
| from cms.utils.urlutils import admin_reverse | |||
There was a problem hiding this comment.
Can we try to organize import statements in some logical order e.g. one recommended in PEP8 (http://legacy.python.org/dev/peps/pep-0008/#id17). It really makes reading and understanding source code much easier. I know that Python can handle randomly ordered import statements but "Beautiful is better than ugly." :-)
There was a problem hiding this comment.
Sorry but the CMS code is so far from PEP8 that this PR really doesn't seem like the right place to fix it.
There was a problem hiding this comment.
I'm not asking to do full PEP8 cleanup in this PR but to at last not make it worse. It costs nothing to put imports in the "right" order but could make django CMS more PEP8 compliant.
|
We still support python 2.6 :) |
…pace Conflicts: cms/templates/cms/toolbar/plugin.html
|
@yakky tests pass now |
|
👍 |
Allow using django CMS with custom admin site
Added a settings
CMS_ADMIN_NAMESPACE(defaults to'admin') to use a non-standardAdminSitewith django CMS.