From c2e0e077fb31ee53bbf06eff749ca0c6e9269844 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Fri, 9 Nov 2007 16:53:20 +0000 Subject: [PATCH] when talking about an imminent 2.5.2c1, the build should identify itself as being some form of 2.5.2 (this is admittedly a bit conservative); we can make this 2.5.2c1 when making the release --- Include/patchlevel.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Include/patchlevel.h b/Include/patchlevel.h index adfb7fb777..a1a98cf8a1 100644 --- a/Include/patchlevel.h +++ b/Include/patchlevel.h @@ -21,12 +21,12 @@ /* Version parsed out into numeric values */ #define PY_MAJOR_VERSION 2 #define PY_MINOR_VERSION 5 -#define PY_MICRO_VERSION 1 -#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_FINAL +#define PY_MICRO_VERSION 2 +#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_ALPHA #define PY_RELEASE_SERIAL 0 /* Version as a string */ -#define PY_VERSION "2.5.1" +#define PY_VERSION "2.5.2a0" /* Subversion Revision number of this file (not of the repository) */ #define PY_PATCHLEVEL_REVISION "$Revision$" -- 2.50.1