On Mon, Aug 16, 2010 at 10:31:11AM +0800, Russell Keith-Magee wrote:
> On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli <mkb...@gmail.com> wrote:
>
> > ?- random api lock (people tend towards complacency)
>
> I'm not entirely certain I understand this point -- or, at least,
> how it would apply to Django.
>
So the interface between backend and object model is one. I suppose
there is an equivalent interface on the template side.
One example that tripped me up: in 1.2, the signature of
BaseDatabaseWrapper __init__() changed.
In 1.1, I had
def __init__(self, settings_dict):
and in 1.2 I needed
def __init__(self, *args, **kwargs):
>
> Our APIs are always locked, since we don't allow backwards incompatible
> API changes.
>
My 1.1 version must have been wrong then.
>
> > ?- punish dev's who don't fix their bugs quickly after api lock
> >
> > (The presentation lacks specifics on the last point. ;)
>
> Which is a big omission.
>
I'm not a dev there, so I don't know. I'm a regular lurker on the
mailing lists though, so it either happens off-list or on-list but
very infrequently.
>
> > Also, hackathons are a great idea. ?A room full of core developers can
> > get a hell of a lot done in a week.
>
> You won't get any argument from me on this one.
>
I wonder if you ran a really targetting fund-raising campaign how much
would come in. I know when the use is specific, it's easier to raise
money. Sounds like if you raised $12k it would get you pretty close.
m
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
