I'd love to see a better way of managing settings in the core of
django. It's a real pain point sometimes for writing and using
pluggable applications and there's a wide range of ways that
application developers try to tackle it. Some have basically no
settings, some plan on users reading the docum
The common use case on my projects is definitely to trim whitespace.
The autostrip decorator I found on djangosnippets (http://
www.djangosnippets.org/snippets/956/) is pretty awesome, but I'd
prefer not to import that into every project and it would be nice to
not call:
> MyForm = autostrip(MyFo
I love the prefix idea. Seems like the best of both worlds. I also
agree that changing the name to either ``prefix`` or ``msg_prefix``
would probably be preferable, to explicitly indicate that the behavior
is different than the standard msg argument.
This would certainly satisfy my use case.
-we
I haven't looked at the proposed patch, but I'd like very much to be
able to add a ``msg`` argument to assertContains and assertRedirects
at least. The point of the msg argument in normal asserts is to give
the person running the tests a quick, high-level indication of what
went wrong or what was
django-schedule is a backend and frontend, just not a CalDAV backend.
The app is definitely more oriented to being stand-alone right now
though, but that's more because of where work has been done than a
design choice I think. There's been some work lately around adding a
slicker UI (JQuery Fullca
> Given that both MEDIA_PREFIX and ADMIN_MEDIA_PREFIX are easily set in
> settings.py, I can't see the issue.
Having sensible default settings is a worthy goal for a lot of
reasons.
> My standard setup sets
> ADMIN_MEDIA_PREFIX to /admin-media/
As this exemplifies, having something other than /
> This is actually pretty much exactly what I had before, it was horribly
> slow! And somehow not nice since you always have to wrap the users
> around and can't just use request.user...
When you say that it was "horribly slow," does that mean you weren't
using caching to skip the DB, or was it s
