I was working at system check framework [1] during this holiday. I've done
some changes that will solve all problems considered in this thread.
Maybe I'm a careless kind of guy, but when I test out new versions of
> Django, reading all of the release notes is rarely the first thing that
> I do...
On 10/01/2013 06:36 AM, Ivan Kharlamov wrote:
> On 09/27/2013 09:01 PM, Carl Meyer wrote:
>> On 09/27/2013 03:07 AM, Ivan Kharlamov wrote:
> Thank you for considering a fix!
>
> Personally, I'd prefer a solution proposed by Shai, which is (5).
I commented in my reply to Shai why I don't think (5)
Hi Shai,
On 09/27/2013 05:42 PM, Shai Berger wrote:
> On Friday 27 September 2013 20:01:00 Carl Meyer wrote:
>> 3) A first-run warning that can be turned off (and presumably would be
>> off by default in new projects). The obvious mechanism for turning it
>> off would be something in settings. Tha
Hi, Carl,
On 09/27/2013 09:01 PM, Carl Meyer wrote:
> Hi Ivan,
>
> On 09/27/2013 03:07 AM, Ivan Kharlamov wrote:
>> Maybe I'm a careless kind of guy, but when I test out new versions of
>> Django, reading all of the release notes is rarely the first thing that
>> I do... my bad. :) My first actio
On Friday 27 September 2013 20:01:00 Carl Meyer wrote:
>
> 1) The status quo. If people run the new "manage.py check" command,
> they'll get a warning directing them to the release notes. But given
> that "manage.py check" is new, its unlikely anyone would run it unless
> they've already read the
Hi Ivan,
On 09/27/2013 03:07 AM, Ivan Kharlamov wrote:
> Maybe I'm a careless kind of guy, but when I test out new versions of
> Django, reading all of the release notes is rarely the first thing that
> I do... my bad. :) My first action is usually firing up the test suites
> and looking at the nu
Hi!
Maybe I'm a careless kind of guy, but when I test out new versions of
Django, reading all of the release notes is rarely the first thing that
I do... my bad. :) My first action is usually firing up the test suites
and looking at the number of failed tests and deprecation warnings.
As we all k