Re: Setting dictionaries (was Re: integrating django-secure)

On Thu, Sep 4, 2014 at 7:36 PM, Collin Anderson wrote: > I'm trying to think outside the box on settings. > > If we want to logically group settings together, what if we supported > syntax like this? > > MIDDLEWARE_CLASSES = ( >

Re: Setting dictionaries (was Re: integrating django-secure)

yeah... I thought of circular imports... you would need to lazy-load most imports. not fun. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Is this a bug?

I'm opening a django console (to narrow the problem) and run this line: for sesion in SesionJuego.objects.filter(preguntas__respuesta__isnull=True): print sesion, sesion.pk Where: * printing is just a sample operation. I'm getting the same error (I'll describe later) with any loop

Re: proposing max line length of 119 + enforcing it with flake8

we say 119 because it's 120 minus one, just like PEP8 recommends 79 because it's 80 minus one. It allows for one character at the beginning of the line for a plus or minus sign in a diff. -- You received this message because you are subscribed to the Google Groups "Django developers" group.

Re: proposing max line length of 119 + enforcing it with flake8

Screenshot for comparison. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving

Re: Proposal: The 'use' template tag, a cross between 'include' and 'extends'.

Hi again, One thing that I wasn't happy with in the implementation I posted yesterday was that you could not override templates included using 'use' in another child template. Effectively all blocks inside the 'use' tag and its included template where invisible outside of it. This needed to be

Re: Proposal: The 'use' template tag, a cross between 'include' and 'extends'.

Curtis, You are welcome to include it in your project and I'm happy to help out. Depending on what happens here I may still release it as a simple standalone app though. I do think this is the kind of thing that would do best in core though as it would ensure that there was a standardised

Re: Models inside test folder - Django 1.7 problem

On 09/04/2014 08:53 AM, galozek wrote: > I'm trying to port my project to Django 1.7. Every goes fine except 1 > problem with an abstract model testing. > Django 1.7 runs migrate command while testing. That means models not > included in migrations are omitted. That's the issue I've got. > > What

Models inside test folder - Django 1.7 problem

Hi, I'm trying to port my project to Django 1.7. Every goes fine except 1 problem with an abstract model testing. Django 1.7 runs migrate command while testing. That means models not included in migrations are omitted. That's the issue I've got. What I do in my /app/tests/ directory: - I

Proposal: add a get_for_template method to ContextList

Hello everyone, while writing a test for a view, I found that one of the rendered templates context had a key used by the main template of the view itself, but with a different value. Given the rendering order, calling response.context[key] would not return the view template context value,

Re: Proposal: The 'use' template tag, a cross between 'include' and 'extends'.

I would like to see someone do a review of the various third party implementations of concepts like this, I think there's a place in core for some variant, it's just working out which one the "right" one is. The other issue with adding new tags to core (especially with "common" names) is name

Re: Proposal: The 'use' template tag, a cross between 'include' and 'extends'.

I really like this idea, and have wanted something similar every time I start a new project and begin building out the main template. I think including this (or something like this) in core is a great idea. Just because it *can* be implemented in 3rd party code, doesn't mean it has to be. On