#12135 closed (fixed)
confusion between get_current_time and do_current_time
| Reported by: | Daniele Procida | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.1 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#setting-a-variable-in-the-context
I think that some of the examples switch between between 'get_current_time' and 'do_current_time' in a confusing way (I got confused, anyway).
Attachments (2)
Change History (5)
by , 15 years ago
| Attachment: | 12135a.diff added |
|---|
by , 15 years ago
| Attachment: | 12135b.diff added |
|---|
comment:1 by , 15 years ago
| Has patch: | set |
|---|---|
| Triage Stage: | Unreviewed → Ready for checkin |
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 15 years ago
Note:
See TracTickets
for help on using tickets.
I agree this is confusing since the name get_current_time is used without warning. I think we could solve this in one of two ways: a) add an example of registering the tag or b) rename the tag to current_time like it is named in the other versions. I'm learning toward b since I don't see a reason to change the name, but I'll leave the decision up to the committer.