"magic-removal" branch merged
We've merged the magic-removal branch to trunk!
All Django development from now on will focus primarily on the branch formerly known as magic-removal, and all documentation on djangoproject.com will focus on the development version.
If you're not familiar with the magic-removal branch, see this previous writeup.
Detailed upgrade instructions are on the RemovingTheMagic wiki page. Please do go ahead and edit that page to add suggestions and clarifications as needed.
Note that this change applies only to Django's development version. If you're using an official release, such as Django 0.91, you won't be affected by this until Django's next release, coming in the near future. It's probably a good idea, however, for you to play around with the development version now to start learning what's changed.
Also, please be aware that the documentation on djangoproject.com now all refers to the new "magic-removal" syntax. With a few exceptions, all of the documentation has been proofread and updated to match the new APIs. (And many documents have been significantly expanded!) Previous versions of the documentation are here: 0.91 (covers 0.91 and development versions up to magic-removal merge) and 0.90 (covers 0.90 and development versions up to 0.91).
We'd like to thank ALL the dozens of people, all over the world, who have submitted code, documentation, bug reports and other help in this branch. Special thanks go to the magic-removal committers, Joseph Kocherans, Russell Keith-Magee and Luke Plant.
So, what's the next step? Let's take care of any new translations that need to be done for the new version in trunk, and then, pending small bugfixes, we'll release 0.95. (In tandem, we'll release 0.92, a "final" version of 0.91 that has a few months' worth of bugfixes applied.)
As always, thanks for using Django.
Posted by Adrian Holovaty on May 1, 2006
Comments
Brantley May 1, 2006 at 10:06 p.m.
Congrats and thank you. Good work fellas.
Jacob May 1, 2006 at 10:09 p.m.
Dave --
if you've been working on the branch, then you've got that exactly right. If you've been on the trunk, then a simple "svn update" will be all you need.
Tony May 2, 2006 at 1:18 a.m.
Well done guys - I've been using MR for a while and it's been terrific!
Now, to do 'svn update' on my own trunk...
CoolGoose May 2, 2006 at 6:35 a.m.
Great news. Go go go with the documentation :D.
Alex Bucur.
Valeriy May 2, 2006 at 4:16 p.m.
Sincere congratulations! I'm using Django for a new project. A few days ago I converted to MR branch, and now it's in the trunk! If it goes like this, my project has a chance to go live on the new sweet stable Django release.
Chris McAvoy May 3, 2006 at 9:15 a.m.
Congratulations Djangoneers! Trunk! Trunk! Trunk!
Will Gunadi May 3, 2006 at 11:59 p.m.
Hmm... the new version doesn't seem to recognize models across multiple files. I know in the wiki it says:
<quote>
Model location changed ΒΆ
In previous Django versions, models lived in a models/ subdirectory of your app package. Now, they should live in a file models.py directly within your app package.
</quote>
First of all, this is a basic Python behavior, how can it not work in Django?
Secondly, why can't I organize my models with multiple files? I have more than 20 models, it's going to be confusing for them to live in one file.
Dan May 4, 2006 at 9 a.m.
huzzah!
Simon Willison June 6, 2006 at 5:21 a.m.
Will: You can keep your models in as many files as you like, then import them in to that one models.py file at the top of the file.
Comments are closed
To prevent spam, comments are no longer allowed after sixty days.
Dave Avraamides May 1, 2006 at 9:33 p.m.
Great news! As an svn newb, what is the *right* way to cut over? Is it:
svn switch http://code.djangoproject.com/svn/dja...
or is there a better way to do it?