Re: newforms.clean_data vs. newforms.cleanED_data

[James Bennett]

On 5/15/07, Malcolm Tredinnick <mal...@pointy-stick.com> 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, but since
there are a lot of folks tracking SVN should we maybe also start using
the Django weblog to announce these? The weekly roundup posts Adrian
used to do seem like an ideal way to also mention any
backwards-incompatible changes in trunk, and I'd imagine there are
already a lot of people reading it regularly and tracking its feed...

--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

[SmileyChris]

Indeed. And I do so miss the weekly roundups ;)

On May 16, 10:35 am, "James Bennett" <ubernost...@gmail.com> wrote:

[Adrian Holovaty]

On 5/15/07, SmileyChris <smile...@gmail.com> 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.com

[sime]

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.

[Fernando Gutierrez H.]

Look at:

http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges

--
Fernando Gutierrez H.

sime escribió: