#19571 closed Cleanup/optimization (fixed)
Django 1.5 Tutorial Need to update Version on First page
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.5-beta-1 |
Severity: | Normal | Keywords: | |
Cc: | timograham@… | Triage Stage: | Accepted |
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/#the-development-server
it says:
Validating models...
0 errors found.
Django version 1.4, using settings 'mysite.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
It should say version 1.5 instead of 1.4
Attachments (1)
Change History (11)
comment:1 by , 12 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 12 years ago
Resolution: | invalid |
---|---|
Status: | closed → new |
Triage Stage: | Unreviewed → Accepted |
Grump... reading too fast. Sorry.
comment:3 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
by , 12 years ago
Attachment: | 19571.diff added |
---|
comment:5 by , 12 years ago
Cc: | added |
---|
An alternative to bumping the version number manually each release would be to use the sphinx substitution |version|. Unfortunately, this doesn't work in code blocks unless you add the parsed-literal directive which eliminates any syntax highlighting. The runserver output isn't highlighted anyway, but the example on docs/intro/install.txt does lose some color. What do you think?
comment:6 by , 12 years ago
I'm in favor of automatic substitution even at the cost of syntax highlighting.
Having to update a bunch of files at each release (and each new year) is annoying.
Maybe we can split the code into smaller blocks to reduce the impact.
If it says 1.4, that does mean that the Django version you are running is 1.4. It may also mean that you have more than one version installed and that the wrong one is running.