Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#11205 closed (fixed)

Tutoria Page 1: django.db.models.Model.__str__() used instead of __str__()

Reported by: WickedMetalHead Owned by: kmtracey
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

On page 1 of the Tutorial there is a info box called "Why unicode() and not django.db.models.Model.str()?". I think this is supposed to be str() and not django.db.models.Model.str(). The box is detailing the reason that django chose to use the unicode method over the typical str method that is usually added to python classes. This is supported by reading the first sentence. If you're familiar with Python, you might be in the habit of adding django.db.models.Model.str() methods to your classes, not unicode() methods.

To fix this i would change the django.db.models.Model.str() to just str()

Change History (3)

comment:1 Changed 6 years ago by kmtracey

  • Needs documentation unset
  • Needs tests unset
  • Owner changed from nobody to kmtracey
  • Patch needs improvement unset
  • Status changed from new to assigned
  • Triage Stage changed from Unreviewed to Accepted

The markup to create the cross-references for __str__ is missing an apparently-required leading ~.

comment:2 Changed 6 years ago by kmtracey

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [10843]) Fixed #11205 -- Made the links to the str method description look the same as the links to the unicode method description in the tutorial part 1. Having one be fully qualified while the other was not was odd-looking.

comment:3 Changed 6 years ago by kmtracey

(In [10844]) [1.0.X] Fixed #11205 -- Made the links to the str method description look the same as the links to the unicode method description in the tutorial part 1. Having one be fully qualified while the other was not was odd-looking.

r10843 from trunk.

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