Navigation

Changeset 4209

Timestamp:

12/15/06 12:07:20 (2 years ago)

Author:

adrian

Message:

Clarified docs/newforms.txt 'Migration plan' section

Files:

r4200	r4209
14	14	release, our plan is to do the following:
15	15
16		* Move the current ``django.forms`` to ``django.oldforms``. This will allow
17		for an eased migration of form code. You'll just have to change your
18		import statements::
	16	* As of revision [4208], we've copied the current ``django.forms`` to
	17	``django.oldforms``. This allows you to upgrade your code now rather
	18	than waiting for the backwards-incompatible change and rushing to fix
	19	your code after the fact. Just change your import statements like this::
19	20
20	21	from django import forms # old
21	22	from django import oldforms as forms # new
22	23
23		* Move the current ``django.newforms`` to ``django.forms``.
	24	* At an undecided future date, we will move the current ``django.newforms``
	25	to ``django.forms``. This will be a backwards-incompatible change, and
	26	anybody who is still using the old version of ``django.forms`` at that
	27	time will need to change their import statements, as described in the
	28	previous bullet.
24	29
25	30	* We will remove ``django.oldforms`` in the release after the next Django
26	31	release -- the release that comes after the release in which we're
27		creating ~~``django.old~~forms``.
	32	creating the new ``django.forms``.
28	33
29	34	With this in mind, we recommend you use the following import statement when