Staging
v0.5.1
v0.5.1
https://github.com/python/cpython
Revision 04eef97a8ac1089bb9f0227a2be38f07c9972268 authored by Ezio Melotti on 27 February 2010, 13:52:50 UTC, committed by Ezio Melotti on 27 February 2010, 13:52:50 UTC
svn+ssh://pythondev@svn.python.org/python/trunk ........ r78489 | ezio.melotti | 2010-02-27 15:50:35 +0200 (Sat, 27 Feb 2010) | 1 line Fix missing parenthesis. ........
1 parent c92fc82
Tip revision: 04eef97a8ac1089bb9f0227a2be38f07c9972268 authored by Ezio Melotti on 27 February 2010, 13:52:50 UTC
Merged revisions 78489 via svnmerge from
Merged revisions 78489 via svnmerge from
Tip revision: 04eef97
patchlevel.h
/* Newfangled version identification scheme.
This scheme was added in Python 1.5.2b2; before that time, only PATCHLEVEL
was available. To test for presence of the scheme, test for
defined(PY_MAJOR_VERSION).
When the major or minor version changes, the VERSION variable in
configure.in must also be changed.
There is also (independent) API version information in modsupport.h.
*/
/* Values for PY_RELEASE_LEVEL */
#define PY_RELEASE_LEVEL_ALPHA 0xA
#define PY_RELEASE_LEVEL_BETA 0xB
#define PY_RELEASE_LEVEL_GAMMA 0xC /* For release candidates */
#define PY_RELEASE_LEVEL_FINAL 0xF /* Serial should be 0 here */
/* Higher for patch releases */
/* Version parsed out into numeric values */
/*--start constants--*/
#define PY_MAJOR_VERSION 2
#define PY_MINOR_VERSION 6
#define PY_MICRO_VERSION 4
#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_FINAL
#define PY_RELEASE_SERIAL 0
/* Version as a string */
#define PY_VERSION "2.6.4+"
/*--end constants--*/
/* Subversion Revision number of this file (not of the repository) */
#define PY_PATCHLEVEL_REVISION "$Revision$"
/* Version as a single 4-byte hex number, e.g. 0x010502B2 == 1.5.2b2.
Use this for numeric comparisons, e.g. #if PY_VERSION_HEX >= ... */
#define PY_VERSION_HEX ((PY_MAJOR_VERSION << 24) | \
(PY_MINOR_VERSION << 16) | \
(PY_MICRO_VERSION << 8) | \
(PY_RELEASE_LEVEL << 4) | \
(PY_RELEASE_SERIAL << 0))
Computing file changes ...
