Opened 11 years ago
Last modified 11 years ago
#20639 closed Cleanup/optimization
Documentation talks about __unicode__() which doesn't exist in Python 3.x anymore — at Initial Version
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | 1.5 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
https://docs.djangoproject.com/en/1.5/intro/tutorial01/
On the above mentioned page, the tutorial tells me to write a unicode() method to get a human-readable represantation of my object. I tried but it didn't work. I then found out that since I'm using Python 3.3 I have to define a method string (). Since there's a block debating whether to use str() or unicode() anyways, may it would be useful to add a hint for Python 3.x users to always use str().
Regards,
Fabian
P.S.: Unfortunately the methodnames beginning with two underscores are interpreted as wiki syntax.
Note:
See TracTickets
for help on using tickets.