Sorry to be late to this thread, I just came across it.
There's another place where the order of INSTALLED_APPS matters: management
commands. Management commands associated with apps that come later in
INSTALLED_APPS will replace those with the same name that are listed
earlier. I can't find
1 Sep 2013 21:31, "Kevin Christopher Henry"
> <k...@severian.com>
> wrote:
>
>> Sorry to be late to this thread, I just came across it.
>>
>> There's another place where the order of INSTALLED_APPS matters:
>> management commands. Management command
>
>
> We probably cannot move checks of `primary_key` and `unique` living in
> `FileField.__init__`. We test if one of these two parameters was passed; we
> don't check their values. Consider that an user passes unique=False. This
> is
> the default value, but nevertheless, this should result in
To summarize the possible approaches here:
1) Combine multiple with statements into one wherever possible. This seems
to be the approach of the commit in question.
2) Group with statements based on whether they logically belong together,
regardless of line length. This will involve backslashes,
I recently upgraded one of my projects to 1.6 and was surprised to find
that some of my tests were failing. I filed a ticket [1], and the
subsequent discussion with Aymeric makes me think that there is a tricky
issue here, worth discussing.
The basic problem is that when using TestCase you
+1 for "is_installed"
I don't find the grammar objectionable here, just think of it as "is_(each
one of these apps)_installed"
On Sunday, January 5, 2014 3:50:45 PM UTC-6, Aymeric Augustin wrote:
>
> On 5 janv. 2014, at 22:38, Raffaele Salmaso
>
> wrote:
>
> > Should
Russell makes the very good point that Jinja2 isn't just a faster version
of the Django template engine - it's philosophically at odds with the
original design and intent of the Django template engine.
Personally, I prefer Jinja2's approach and would love to see it become the
standard. (The
Hi Christopher,
> ... checks the template extension and dispatch to
> corresponding function from `django.dtl` or `jinja2`.
>
The mechanism for distinguishing the two kinds of template needs to be more
flexible. For example, let's say I want to override a third-party template
with my own
>
> What kind of support do you except for third-party template tags? Suppose,
> that
> `cycle` tag is not builtin. Would it be acceptable to write sth like that:
>
> dtl cycle '1' '2' as rows
>
> It could be quite easily implemented as a Jinja2 extensions. Of course, I
> guess
> that you'd
This issue was the subject of https://code.djangoproject.com/ticket/24082.
There, the accepted (but not implemented) solution is the same as suggested
here: allowing the user to opt out of the creation of the additional index
with `db_index=False`.
On Wednesday, April 15, 2015 at 2:11:25 PM
Hello,
With all the talk of DEPs flying around I thought I'd finally take a look
at one in detail.
I wanted to make a suggestion about it and realized that there wasn't
really a good place to do so. The issue was too minor for a mailing list
discussion, and there was no open pull request to
If anyone's put off by the hectoring tone of the imperative mood, it might
be better to think of it as the indicative mood. That is:
(This will) "add password validation to prevent the usage of...".
rather than
(You must) "add password validation to prevent the usage of..."!
In English
Regarding venv and bash, I filed a ticket [1] three years ago to have the
bash script included with the Windows venv installation, and it looks like
that change is in from 3.5 on. So in any case we shouldn't need to suggest
virtualenv any more.
Although I personally use bash, I definitely
13 matches
Mail list logo