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

diff --git a/Include/patchlevel.h b/Include/patchlevel.h
index adfb7fb77786d762c9c2f7f654289b580520e2f9..a1a98cf8a1854f11eb656a06796d6c6c8fc3a553 100644 (file)
--- 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$"