Look at:
http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
--
Fernando Gutierrez H.
sime escribió:
> Perhaps even a single page, that lists all backwards-incompatible
> changes, by their version of introduction to trunk? I've already used
> newforms in production, so stuff like th
Perhaps even a single page, that lists all backwards-incompatible
changes, by their version of introduction to trunk? I've already used
newforms in production, so stuff like this is kinda important.
--~--~-~--~~~---~--~~
You received this message because you are s
On 5/15/07, SmileyChris <[EMAIL PROTECTED]> wrote:
> Indeed. And I do so miss the weekly roundups ;)
If somebody wants to volunteer to write the weekly roundups, let me
know. I've been extremely swamped lately (but it's getting better).
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.co
Indeed. And I do so miss the weekly roundups ;)
On May 16, 10:35 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 5/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > It's probably more important to check the web page than follow the
> > developers' list, I would say. It's a bug if we
On 5/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> It's probably more important to check the web page than follow the
> developers' list, I would say. It's a bug if we don't update the webpage
> after a real incompatible change.
I've posted a followup reminder to django-users about this,
