Sounds like a spot where we might be able to improve the documentation.
On Sunday, February 1, 2015 at 10:33:09 AM UTC-5, Markus Amalthea Magnuson
wrote:
>
> Which is, I guess, why it is the block tag's behavior that would need to
> change rather than the if tag's, if support for blocks inside i
Which is, I guess, why it is the block tag's behavior that would need to
change rather than the if tag's, if support for blocks inside if tags were
to be implemented.
Have not had a look myself at this though, but I too was confused the first
few times I tried to put blocks in if statements and no
Hi,
Am Sat, 31 Jan 2015 22:36:05 +0100
schrieb Aymeric Augustin :
> I suspect it has to do with {% if %} being interpreted at runtime
> while {% block %} is interpreted at compile time.
>
> I never investigated this fully. If someone does, I’m interested :-)
This was my guess as well. However, i
I don't think there is enough time in GSOC to properly extract so many
components into separate packages. I don't even know if this would be a
long term goal for Django. Even if it were, there's more to it than just
creating a new repository. Maintainers would have to put their hand up to
manag
Hi,
For the Reducing coupling of Django components project I have some broader
Aim and objectives in my which I am planning to propose.
The main goal of this project proposal is to lay down the stepping stones
for reducing coupling in django internal components. To achieve the goal
1. Analyze an
