Re: changing the on_delete=CASCADE default

After far too long, this ticket has been created: https://code.djangoproject.com/ticket/21961 If there's general consensus that this feature is worth working on, I'll see about a 1.7-targeted patch for it. On Sep 28, 2013, at 10:16 AM, Anssi Kääriäinen wrote: > > > On Saturday, Sept

Re: Check Framework Feedback

Hi Curtis, The catch is that a hint isn't always possible - or the only reasonable hint would be redundant. For example: ERROR: max_length exceeds 100. HINT: Make max_length less than 100. The hint doesn't actually clarify anything above what the error message already tells you. You can see

Re: Check Framework Feedback

I disagree. If a hint really ought be provided, but can be omitted in the right circumstances, it should be a required value. This will encourage people to provide a hint, or deliberately omit one. Seems more Explicit and Implicit to me... explicit intention to omit a hint? -- Curtis On 6 Fe

Re: GSoC Project Ideas

On Thu, Feb 6, 2014 at 7:35 AM, Cody Scott wrote: > The Google Summer of Code 2014 Project Ideas seems to be outdated. > > https://code.djangoproject.com/wiki/SummerOfCode2014 > > > Hi Cody, Yes - both these projects are still relevant. > Test framework cleanup - Is this still relevant with th

Re: Check Framework Feedback

On Thursday, February 6, 2014 12:31:43 AM UTC+1, Carl Meyer wrote: > > > However, I can see how this might be slightly contrary to expectation > > for Python developers generally. I'd be interested in hearing other > > opinions on this. > > I don't think there's a reason to require the argumen

GSoC Project Ideas

The Google Summer of Code 2014 Project Ideas seems to be outdated. https://code.djangoproject.com/wiki/SummerOfCode2014 Test framework cleanup - Is this still relevant with the new Django 1.6 django-discover-runner?Improved error reporting - Is this still relevant with the new validations in

Re: Check Framework Feedback

On 02/05/2014 04:14 PM, Russell Keith-Magee wrote: > On Wed, Feb 5, 2014 at 10:13 PM, Thomas Güttler > wrote: > > Hi, > > here is some feedback to the check framework, documented at: > > https://docs.djangoproject.__com/en/dev/ref/checks/ >

Re: Check Framework Feedback

Hi Thomas, On Wed, Feb 5, 2014 at 10:13 PM, Thomas Güttler wrote: > Hi, > > here is some feedback to the check framework, documented at: > > https://docs.djangoproject.com/en/dev/ref/checks/ > > --- > > > {{{ > Error('error message', None) # Good > }}} > > I don't think this is "good". The "hint

Fwd: Syncdb issue

Hello everyone, As we all know that syncdb is the command used in django to create tables and we also know that it does mot update tables once it is created. But why does it happen? Has anyone thought about it? For updating it we need to use south and django migrations. Actually I want to do improv

Re: Syncdb issue

Hi Harjot, syncdb has in fact been deprecated in 1.7 and replaced with migrate [1], so what you propose has already been accomplished! Andrew [1]: https://docs.djangoproject.com/en/dev/releases/1.7/#schema-migrations On Wed, Feb 5, 2014 at 6:35 PM, Harjot Mann wrote: > Hello everyone, > As we

Check Framework Feedback

Hi, here is some feedback to the check framework, documented at: https://docs.djangoproject.com/en/dev/ref/checks/ --- {{{ Error('error message', None) # Good }}} I don't think this is "good". The "hint" should be optional. The above line is ugly, since you don't know why there is second arg