Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / python / cpython3 / 0b89fc02140a4503766a973c219f85f1ee3285bb / . / PCbuild / BUILDno.txt
blob: 303c37eb3451389ba9572345ad89c771d3412f81 [file] [log] [blame]
Tim Petersfc9eeae2000-09-07 08:28:50 +0000[diff] [blame]1Python has a "build number" scheme on Unix-like systems that's hard to
2explain:
3
4Python 2.0b1 (#4, Sep 7 2000, 02:40:55) [MSC 32 bit (Intel)] on win32
5 ^^
6The build number there is "#4".
7
8Each developer's unique build tree generates its own "build numbers",
9starting at 0, and increasing by 1 each time a build is done in that tree.
10These numbers are never checked in, or coordinated in any other way. It's
11just handy for a developer to distinguish among their own personal builds.
12
13The makefile tricks used to accomplish this under Unix-like systems don't
14work under MSDev. Here we fake it by hand, but much less frequently, and
15do check it in. The build number only changes often enough to distinguish
16releases from each other, and from the long "in between" stretches of CVS
17development. An account of all Windows BUILD numbers follows; when you
18check in a new one, please add an entry to the top of the list.
19
20How to change the Windows build number:
21
22+ Right-click on getbuildinfo.c from within MSDev. Select Settings ...
23+ Select the General category of the C/C++ tab.
24+ In "Settings For:" select "Multiple Configurations ...".
25+ Check the "Win32 Release" and "Win32 Debug" boxes and click OK.
26+ In the Preprocessor Definitions box, increment the number after BUILD=.
27+ Click OK.
28+ This is not enough to convince MSDev to recompile getbuildinfo.c,
29 so force that and relink.
Tim Peters68692452000-10-14 07:35:15 +0000[diff] [blame]30+ Verify that the new build number shows up in both release and debug
Tim Petersfc9eeae2000-09-07 08:28:50 +0000[diff] [blame]31 builds.
32
33
34Windows Python BUILD numbers
35----------------------------
Tim Peters0b89fc02001-07-20 05:17:10 +0000[diff] [blame^]36 21 2.2a1
Tim Peters0eb4f3e2001-07-17 04:05:43 +0000[diff] [blame]37 18-Jul-2001
Tim Peters0b89fc02001-07-20 05:17:10 +0000[diff] [blame^]38 20 2.1.1
Tim Peters87349522001-07-02 04:08:39 +0000[diff] [blame]39 20-Jul-2001
Tim Petersc683a292001-07-14 03:31:35 +0000[diff] [blame]40 19 2.1.1c1
Tim Peters87349522001-07-02 04:08:39 +0000[diff] [blame]41 13-Jul-2001
Tim Peters289a9612001-06-22 02:06:04 +0000[diff] [blame]42 18 2.0.1
43 22-Jun-2001
Tim Peters42107c52001-06-13 19:17:32 +0000[diff] [blame]44 17 2.0.1c1
45 13-Jun-2001
Tim Peters52709e32001-04-18 21:12:25 +0000[diff] [blame]46 16 CVS development
47 18-Apr-2001
48 15 2.1 final
Tim Petersdd37dac2001-04-16 18:20:30 +0000[diff] [blame]49 16-Apr-2001
Tim Petersb0931662001-04-16 01:44:08 +0000[diff] [blame]50 14 2.1c2
51 15-Apr-2001
Tim Petersfd09e862001-04-12 04:01:39 +0000[diff] [blame]52 13 2.1c1
53 12-Apr-2001
Tim Peters55f826c2001-03-21 06:09:14 +0000[diff] [blame]54 12 2.1b2
55 20-Mar-2001
Tim Peters5f850ab2001-03-01 02:43:40 +0000[diff] [blame]56 11 2.1b1
57 28-Feb-2001
Tim Petersca873ed2001-02-01 05:10:02 +0000[diff] [blame]58 10 2.1a2
59 1-Feb-2001
Tim Peters97c96402001-01-17 23:23:13 +0000[diff] [blame]60 9 2.1a1
61 17-Jan-2001
Tim Peters68692452000-10-14 07:35:15 +0000[diff] [blame]62 8 2.0 (final)
63 14-Oct-2000
Tim Peters70d87d72000-10-07 04:04:07 +0000[diff] [blame]64 7 2.0c1
65 07-Oct-2000
Tim Petersf1fcc812000-09-25 21:55:28 +0000[diff] [blame]66 6 2.0b2
67 26-Sep-2000
Tim Petersfc9eeae2000-09-07 08:28:50 +0000[diff] [blame]68 5 CVS development
69 07-Sep-2000
70 4 2.0b1 repaired to include Lib\xml + Lib\lib-old + Lib\test\*.xml
71 07-Sep-2000
72 3 2.0b1
73 05-Sep-2000
74 2 CVS development
75 1 unused
76 0 2.0b1p1 and 2.0b1p2
77 01-Sep-2000 for both -- this scheme hadn't started yet