On Thursday, 5 April 2012 21:25:19 UTC+5:30, Andrew Godwin wrote:
>
> If you plan to continue using
> Django fields as type information (as South does), what potential issues
> do you see there?
>
The only issue I can think of is the case of custom fields created by the
user.
--
You received
On Thursday, 5 April 2012 21:25:19 UTC+5:30, Andrew Godwin wrote:
>
> Just thought I'd chime in now I've had a chance to look over the current
> proposal (I looked at the current one you have in the GSOC system):
>
> - When you describe feeding things in from local_fields, are you
> referring
On Tuesday, 3 April 2012 06:39:37 UTC+5:30, Russell Keith-Magee wrote:
>
>
> On 03/04/2012, at 5:06 AM, j4nu5 wrote:
>
> > Hi Russell,
> >
> > Thanks for the prompt reply.
> >
> > * You aren't ever going to eat your own dogfood. You're spending the
>
I have written a patch for ticket #16304 (https://
code.djangoproject.com/ticket/16304).
The ticket adds support for the HTML5 input placeholder attribute
(WHAT Working Group placeholder description -
Hi,
Google Summer of Code 2012 has been announced.
http://google-opensource.blogspot.com/2012/02/google-summer-of-code-2012-is-on.html
I want to work on extending Django's database migration capabilities,
as a student.
Database migrations have always been a pain in Django and most people
rely
