Status of open sourced Django Book?

[Skip Montanaro]

I was encouraged to see that the Django Book authors had open-sourced the book.  I cloned the git repo and built it.  I've been working my way through the online book and thought the open source content might have some updates, but after comparing a couple chapters (intro and Chapter 11), it seems that perhaps nothing has been updated.

Did I just make too small a comparison?  Are the various versions' release notes the only places to find summaries of what's changed since the book was written (for 1.1)?

Thanks,

Skip Montanaro

[Russell Keith-Magee]

On Mon, Jan 14, 2013 at 1:13 AM, Skip Montanaro <skip.mo...@gmail.com> wrote:

I was encouraged to see that the Django Book authors had open-sourced the book.  I cloned the git repo and built it.  I've been working my way through the online book and thought the open source content might have some updates, but after comparing a couple chapters (intro and Chapter 11), it seems that perhaps nothing has been updated.

Did I just make too small a comparison?  Are the various versions' release notes the only places to find summaries of what's changed since the book was written (for 1.1)?

Essentially, yes. To the best of my knowledge, there haven't been any major changes to the Django Book since it was originally published. One of the reasons for releasing the book as open source was to allow (and encourage) the community to submit updates. I'm pretty certain that there weren't that many updates prior to the book source being put on GitHub, so the Github commit history will show you all the changes that have been made. 

If you do go through the release notes for 1.1,  1.2, 1.3 and 1.4, you shouldn't find *that* many backwards incompatibilities. Off the top of my head, I can only think of a few items that would make a significant difference to the content of the Django book:

 * Import syntax at the top of urls.py

 * Quoting syntax in {% url %} tags

 * The method of installing admin urls

 * Allowing for CSRF in forms

There have been other backwards incompatibilities, but they tend to be fairly esoteric edge cases; there have also been lots of additional features, which means the current content of the Django book may not reflect best practice (e.g., the syntax of {% if %} clauses in templates). However, as a project, we've been strict about backwards compatibility, so there shouldn't be much that doesn't work *at all*.

That said, we would certainly welcome any contributions to help get the Django Book up to date, reflecting current best practice, and ironing out the incompatibilities that have emerged over time.

Yours,

Russ Magee %-)

[Skip Montanaro]

If you do go through the release notes for 1.1,  1.2, 1.3 and 1.4, you shouldn't find *that* many backwards incompatibilities.

Thanks.  I wasn't actually all that worried about incompatibilities.  I was more worried about interesting new features in later versions which aren't discussed in the book (or tutorials).  I'm rummage through the release notes and see what I come up with.

Or are new useful features more likely to be found in contributed apps/modules?  If so, how do I browse that environment?  Is there some sort of announce list where new toys tend to pop up?

Skip

[Lachlan Musicman]

On Tue, Jan 15, 2013 at 5:55 AM, Skip Montanaro <skip.mo...@gmail.com> wrote:

book (or tutorials).  I'm rummage through the release notes and see what I come up with.

Or are new useful features more likely to be found in contributed apps/modules?  If so, how do I browse that environment?  Is there some sort of announce list where new toys tend to pop up?

Not really, there is the dev list - but you would need to scan it.

I would recommend the Release Notes - in those you will find the full list of deprecations, backwards incompatible cchanges and new toys, with links to documentation where necessary

https://docs.djangoproject.com/en/dev/releases/

Cheers

L.

--
...we look at the present day through a rear-view mirror. This is something Marshall McLuhan said back in the Sixties, when the world was in the grip of authentic-seeming future narratives. He said, “We look at the present through a rear-view mirror. We march backwards into the future.”

http://www.warrenellis.com/?p=14314