Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#17171 closed Cleanup/optimization (fixed)

No updated tutorial for django 1.3.1

Reported by: haimunt@… Owned by: nobody
Component: Documentation Version: 1.3-rc
Severity: Normal Keywords: url update tutorial
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I have been going through the tutorial for 1.3 (currently the most up-to-date tutorial as far as I know) and have been noticing subtle differences between the tutorial material and the items within my 1.3.1 source files.

One example of this is within the file, the tuples are all wrapped in a 'url' function. This change does not seem to be discussed or reflected in the tutorial at all.

Although these subtle differences are not a big deal (as they are sufficiently demonstrated within the source and are pretty self-explanatory), I just wanted to let you guys know that the differences exist.

Thanks for the great framework!

Change History (4)

comment:1 Changed 7 years ago by anonymous

comment:2 Changed 7 years ago by Carl Meyer

In [17073]:

(The changeset message doesn't reference this ticket)

comment:3 Changed 7 years ago by Carl Meyer

Resolution: fixed
Status: newclosed

In [17074]:

[1.3.X] Fixed #17171 -- Updated tutorial code snippets to match startproject template and recommended practice. (No 'import *', use 'urls()' function.). Thanks haimunt for report.

Parts of this are a backport of r17073 from trunk.

comment:4 Changed 7 years ago by Carl Meyer

Triage Stage: UnreviewedAccepted

Thanks for the report! I've fixed the URLconf inconsistencies you mentioned, and am closing this ticket fixed, as it won't help us very much to have an open-ended ticket. The 1.3 docs on the site are actually the latest docs from the 1.3.X branch, and should be up to date with 1.3.1 - where they aren't, that's a bug. If you see other inconsistencies as you run through the tutorial, please do report them in another ticket! (It's ok to group everything you find into one ticket).

Note: See TracTickets for help on using tickets.
Back to Top