Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#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)

19571.diff (1.4 KB) - added by timo 2 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 2 years ago by claudep

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

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.

comment:2 Changed 2 years ago by claudep

  • Resolution invalid deleted
  • Status changed from closed to new
  • Triage Stage changed from Unreviewed to Accepted

Grump... reading too fast. Sorry.

comment:3 Changed 2 years ago by Claude Paroz <claude@…>

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

In a890469d3bffe267aed0260fd267e44e53b14c5e:

Fixed #19571 -- Updated runserver output in the tutorial

comment:4 Changed 2 years ago by Claude Paroz <claude@…>

In 7ca9b7162830218c299aa1132bca9781ce1e4e90:

[1.5.x] Fixed #19571 -- Updated runserver output in the tutorial

Backport of a890469d3 from master.

Changed 2 years ago by timo

comment:5 Changed 2 years ago by timo

  • Cc timograham@… 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 Changed 2 years ago by aaugustin

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.

comment:7 Changed 2 years ago by Tim Graham <timograham@…>

In 1884868adcc6945afaf7a96e01d35eafb623b847:

Added sphinx substitutions in place of hardcoded version numbers.

Refs #19571

comment:8 Changed 2 years ago by Tim Graham <timograham@…>

In 7c39e041b1e107f437f61e97a11ce9e011d9ad2b:

[1.5.x] Added sphinx substitutions in place of hardcoded version numbers.

Refs #19571

Backport of 1884868adc from master

comment:9 Changed 2 years ago by Claude Paroz <claude@…>

In 7ca9b7162830218c299aa1132bca9781ce1e4e90:

[1.5.x] Fixed #19571 -- Updated runserver output in the tutorial

Backport of a890469d3 from master.

comment:10 Changed 2 years ago by Tim Graham <timograham@…>

In 7c39e041b1e107f437f61e97a11ce9e011d9ad2b:

[1.5.x] Added sphinx substitutions in place of hardcoded version numbers.

Refs #19571

Backport of 1884868adc from master

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