Thank you for any advice.
Regards
Michal
this one
--
regards
kg
http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!
However it does have problems. And when 0.92 comes out you will have to
change to the new syntax anyways. So if your starting from scratch like
me, and your willilng to put up with a few bugs, the magic removal is
the way to go. If however you need rock solid, the trunk is the way to
go.
If you plan to deploy anytime in the next month or two (yes, this is a
real possibility with Django!), you should start with trunk but settle
on a revision before you get too far into the project. I wouldn't
recommend updating from trunk once you've deployed until you've done
very extensive testing, and then I would still only recommend it if you
see some benefit from the update.
-rob
Go with the latest trunk development -- it's the most stable and has
the latest non-magic-removal features. The magic-removal branch is
still for living-on-the-edge developers at this point.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com | chicagocrime.org
month or two? you mean there are people out there who take up to a
*month* to deploy a django app??
The problem I see with the m-r path for a newbie is that all the
docs, tutorials, and examples are pre-m-r ... so starting from
scratch with the m-r means a lot more headaches in learning
Django.
--
Glenn Tenney