Re: confusing things in Trac UI (was: Design decision for #1625...)

On Sun, Sep 25, 2011 at 12:06 AM, Luke Plant wrote: > On 21/09/11 10:40, Stephen Burrows wrote: > >> Just thought it might be worth mentioning in this thread that django- >> ticketeer is coming along nicely. (For those who don't know, django- >> ticketeer is a django

Re: Revisiting proxied SSL headers

On 24/09/11 19:34, Carl Meyer wrote: > On 09/24/2011 09:02 AM, Luke Plant wrote: >> It is a tricky problem, because I don't know of any perfect solution. My >> concern is not only that it is possible to configure incorrectly, it >> appears to be virtually impossible to configure correctly, as it

Re: Revisiting proxied SSL headers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/24/2011 09:02 AM, Luke Plant wrote: > It is a tricky problem, because I don't know of any perfect solution. My > concern is not only that it is possible to configure incorrectly, it > appears to be virtually impossible to configure correctly, as

Re: confusing things in Trac UI (was: Design decision for #1625...)

On 21/09/11 10:40, Stephen Burrows wrote: > Just thought it might be worth mentioning in this thread that django- > ticketeer is coming along nicely. (For those who don't know, django- > ticketeer is a django front-end for trac installations which was > spawned during the djangocon sprints). It

Re: new feature idea: even and odd forloop iteration variables

Hi skazhy, > I've been working with Django for a while now, but today I decided to > make a first contribution to Django that would make templates less > ugly by adding these two values to loop_dict (in django/template/ > defaulttags.py): > > loop_dict['even'] = (i %2 == 0) > loop_dict['odd'] =

Re: Revisiting proxied SSL headers

On 24/09/11 01:06, Paul McMillan wrote: > CarlJM's django-secure package [4] solves this problem by requiring > the user to specify which header they want, if they need support for > this. > > Luke's concerns about the security of this setting are extremely well > founded. Enabling it when it is

Check-in #3 / Multiple timezone support for datetime representation

Hello, This week, I've been working on a related topic that I had missed entirely in my initial proposal: serialization. Developers will obtain aware datetimes from Django when USE_TZ = True. We must ensure that they serialize correctly. Currently, the serialization code isn't very consistent

Re: Localization on User model

On Thu, Sep 22, 2011 at 1:52 PM, Aymeric Augustin wrote: > 2011/9/22 lvella : >> What about changing this in future versions? Maybe simply a >> "true_name" field would do? Or maybe a way to customize the fields in >> the User model. > > Hi

Re: API for introspecting models

It might be worth it to look at this existing effort to document _meta: http://readthedocs.org/projects/django-model-_meta-reference/. Simon -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: API for introspecting models

Ok :) Honestly, I don't have that much time, so I can't promise to look actively into that (but I guess that's no big deal). Of course, if Justin helps it sounds like a more reasonable task :) Anyways, I could perfectly start with the first step : > a rough cut at documenting everything that is

Re: API for introspecting models

Very interesting / exciting. I'm definitely +1 on this project - I definitely have some of the "break hard" projects that Russell is talking about and I'd love to have a more straightforward and sustainable way to do introspection. Let me know how I can help. On Fri, Sep 23, 2011 at 10:47 PM,