Accommodate new version numbering scheme.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@17532 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2012-02-16 04:01:58 +00:00
parent 46671e9b68
commit 50c64ed379
2 changed files with 18 additions and 1 deletions

View File

@ -24,6 +24,23 @@ and we've `begun the deprecation process for some features`_.
.. _backwards incompatible changes: `Backwards incompatible changes in 1.4`_
.. _begun the deprecation process for some features: `Features deprecated in 1.4`_
Version numbering
=================
Internally, Django's version number is represented by the tuple
``django.VERSION``. This is used to generate human-readable version
number strings; as of Django 1.4 beta 1, the algorithm for generating
these strings has been changed to match the recommendations of `PEP
386 <http://www.python.org/dev/peps/pep-0386/>`. This only affects the
human-readable strings identifying Django alphas, betas and release
candidates, and should not affect end users in any way.
For example purposes, the old algorithm would give Django 1.4 beta 1 a
version string of the form "1.4 beta 1". The new algorithm generates
the version string "1.4b1".
Python compatibility
====================

View File

@ -75,7 +75,7 @@ setup(
author = 'Django Software Foundation',
author_email = 'foundation@djangoproject.com',
description = 'A high-level Python Web framework that encourages rapid development and clean, pragmatic design.',
download_url = 'https://www.djangoproject.com/m/releases/1.4/Django-1.4-beta-1.tar.gz',
download_url = 'https://www.djangoproject.com/m/releases/1.4/Django-1.4-b1.tar.gz',
packages = packages,
cmdclass = cmdclasses,
data_files = data_files,