Re: ANNOUNCE: Django 1.5 release candidate 2, Django 1.4.4, Django 1.3.6 (security releases)

2013-02-20 Thread Carl Meyer
On Feb 20, 2013, at 6:25 PM, Ian Kelly wrote: > On Feb 20, 2013 4:41 PM, "Carl Meyer" wrote: > > On 02/20/2013 04:25 PM, Nick Phillips wrote: > > >> There was extensive back-and-forth discussion of this in writing the > > >> patch. The issue is that in almost all cases the correct value of the >

'Change' button for related fields.

2013-02-20 Thread Mason Staugler
I was going to monkey patch this into our system until a coworker suggested contributing. This patch will add a 'change' link (next to the 'add' button) for related fields. Is it a trivial patch? I have a feeling it's a Design Decision Needed and the docs suggested post it to this group. Here'

Re: ANNOUNCE: Django 1.5 release candidate 2, Django 1.4.4, Django 1.3.6 (security releases)

2013-02-20 Thread Ian Kelly
On Feb 20, 2013 4:41 PM, "Carl Meyer" wrote: > > On 02/20/2013 04:25 PM, Nick Phillips wrote: > >> There was extensive back-and-forth discussion of this in writing the > >> patch. The issue is that in almost all cases the correct value of the > >> setting in local development and under test are di

Re: ANNOUNCE: Django 1.5 release candidate 2, Django 1.4.4, Django 1.3.6 (security releases)

2013-02-20 Thread Carl Meyer
On 02/20/2013 04:25 PM, Nick Phillips wrote: >> There was extensive back-and-forth discussion of this in writing the >> patch. The issue is that in almost all cases the correct value of the >> setting in local development and under test are different from the >> correct value in production. So how

Re: ANNOUNCE: Django 1.5 release candidate 2, Django 1.4.4, Django 1.3.6 (security releases)

2013-02-20 Thread Nick Phillips
On Tue, 2013-02-19 at 15:46 -0700, Carl Meyer wrote: > Hi Nick, > > On 02/19/2013 03:32 PM, Nick Phillips wrote: > > I don't recall looking at the ALLOWED_HOSTS setting before. Now that I > > do, it seems rather problematic. In particular, that host verification > > is apparently turned off while

ANNOUNCE: Django 1.4.5, 1.3.7 released, fixing packaging problems

2013-02-20 Thread Jacob Kaplan-Moss
Hi folks -- We've released two new releases today -- Django 1.4.5 and Django 1.3.7 -- that correct packaging problems in yesterday's security releases. There's no new code; just a packaging fix. For more details, see https://www.djangoproject.com/weblog/2013/feb/20/updated-releases-issued/. Sorr

Re: Django 1.4.4 and contrib/sessions/management/__init__.pyc

2013-02-20 Thread Carl Meyer
We've just released 1.3.7 and 1.4.5 to correct this packaging problem: https://www.djangoproject.com/weblog/2013/feb/20/updated-releases-issued/ Thanks for reporting it! Carl On 02/19/2013 08:12 PM, Nick Popoff wrote: > I downloaded Django 1.4.4 this evening and after switching to it started >

Re: ANNOUNCE: Django 1.5 release candidate 2, Django 1.4.4, Django 1.3.6 (security releases)

2013-02-20 Thread Carl Meyer
On 02/20/2013 01:58 AM, Reinout van Rees wrote: > On 19-02-13 23:32, Nick Phillips wrote: >> I don't recall looking at the ALLOWED_HOSTS setting before. > > Should there be a note in the 1.4 docs that the default ['*'] value is a > temporary default value? That from 1.5 onwards it will be an emp

Re: clarification of API backwards-compatibility policy

2013-02-20 Thread Jannis Leidel
On Tue, Feb 19, 2013 at 10:56 PM, Carl Meyer wrote: > Hi, > > I was just about to tell someone on IRC that Django's > backwards-compatibility policy only applies to documented methods and > attributes (which is how I'd always understood it), but when I actually > went to look at the documented po

Re: ANNOUNCE: Django 1.5 release candidate 2, Django 1.4.4, Django 1.3.6 (security releases)

2013-02-20 Thread Reinout van Rees
On 19-02-13 23:32, Nick Phillips wrote: I don't recall looking at the ALLOWED_HOSTS setting before. Should there be a note in the 1.4 docs that the default ['*'] value is a temporary default value? That from 1.5 onwards it will be an empty list? https://docs.djangoproject.com/en/1.4/ref/sett