On Mon, Mar 26, 2012 at 7:28 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote:
> Once upon a time -- way back in Django's past -- we actually did have the > tutorial code available as part of the Django repository. The problem was > keeping the tutorial code and the tutorial itself in sync. If the two ever > diverged (because someone made a change and forgot to update the code) or > if there was ever an error in the code, then anyone doing the tutorial > would get confused -- and that's the worst possible time to get confused, > since it's our opportunity to convince someone how good Django is. > > There's also the problem that the tutorial goes through 4 steps, and it > would be useful to have the code at the end of each step of the tutorial. > Maintaining 4 tutorial codebases is also a time consuming process. > There's a middle ground: add enough metadata to the tutorial that its instructions can be interpreted by a machine. One could imagine a build script that parses the tutorial docs and produces four templates suitable for 1.4's project templating system, in much the way that the ALFS project<http://www.linuxfromscratch.org/alfs/> takes its build instructions from the Linux From Scratch documentation intended for humans. That said, it does seem counterproductive to give people shortcuts past the fundamentals, especially when the fundamentals are already so carefully curated. If you want the tutorial code as a reference, the tutorial itself is an excellent textual description of all the changes made, so why not just refer to that? Best, Alex Ogier -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
