djangosnippets.org: Latest snippets tagged with 'deprecated'http://djangosnippets.org/tags/deprecated/2008-10-30T04:34:00.184436-05:00Database Schema Upgrade (deprecated)
2008-10-30T04:34:00.184436-05:00guettlihttp://djangosnippets.org/snippets/1160/<p>Deprecated! I use south in all applications with database backend now.</p>
Freely redistributablecheck if form has changed (deprecated)
2008-02-28T02:29:29.790486-06:00guettlihttp://djangosnippets.org/snippets/621/<p>This is deprecated. I don't use it anymore, since forms now have the attribute "has_changed".</p>
<p>The method form_changed() returns a boolean value. It is True if the submitted
values of the bound and valid form are different than the initial values.</p>
<p>It works for me. Feedback welcome.</p>
<p>Set debug=True if …</p>
Freely redistributablenewforms and ModelForm
2008-01-01T13:38:16.457132-06:00danfairshttp://djangosnippets.org/snippets/530/<p>I noticed that form_for_* in newforms now carry deprecation warnings. This code is a minimal demonstration of how to use ModelForm as a replacement.
</p>
<p>Full information can be found on <a href="http://www.stereoplex.com/two-voices/django-modelform-and-newforms">Stereoplex</a>. Hope this helps you.
</p>
Freely redistributable