Hi everyone!
I think this is probably my first post here! Anyway... I was recently
working on a
django project where I was asked to change the admin theme (just the
colors).
I did so using CSS custom properties (see [1]) so that I would have all the
colors[2] set
in one file.
I'd like to start a
At present, we have a number of functions in django.test.utils which aren't
documented and are meant for use in Django's test suite. Things like:
* extend_sys_path()
* isolate_lru_cache()
* captured_stdout()/err()/in()
* freeze_time()
* require_jinja2()
I have the need to reuse a WidgetTestCase
Hey Tim,
I think we can make a case for including this in django/tests/testcases.py
and in a new module tests/utils/something.py which is then only available
within Django's own the test suite. I think we should include that test
case as part of Django's own test suite for now. It's IMO easier
I'd like to take another try at this.
My proposal is to temporarily supports two formats: the new
`app_label.model_name.codename` (ref #25281) and the old `app.codename`.
The old format will raise a PendingDeprecationWarning. Docs, code and tests
will be updated to use the new format.
I belie
Thanks for introducing me to a new CSS feature! I clearly don't keep up
with front end stuff enough.
Re: your issues:
1. From the support grid at the bottom of the Smashing Magazine article you
linked, it looks like it's only IE 11 and Edge 14 that are major browsers
that don't support it. Howeve
