Text of peps.python.org › pep-0102 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PEP 102 – Doing Python Micro Releases | peps.python.org

PEP 102 – Doing Python Micro Releases PEP 102 – Doing Python Micro Releases Author : Anthony Baxter <anthony at interlink.com.au>, Barry Warsaw <barry at python.org>, Guido van Rossum <guido at python.org> Status : Superseded Type : Informational Created : 09-Jan-2002 Post-History : Superseded-By : 101 Table of Contents Replacement Note Abstract How to Make A Release What Next? Final Release Notes Windows Notes Copyright Replacement Note Although the size of the to-do list in this PEP is much less scary than that in PEP 101 , it turns out not to be enough justification for the duplication of information, and with it, the danger of one of the copies to become out of date.

Therefore, this PEP is not maintained anymore, and micro releases are fully covered by PEP 101 . Abstract Making a Python release is an arduous process that takes a minimum of half a day’s work even for an experienced releaser. Until recently, most – if not all – of that burden was borne by Guido himself. But several recent releases have been performed by other folks, so this PEP attempts to collect, in one place, all the steps needed to make a Python bugfix release.

The major Python release process is covered in PEP 101 - this PEP is just PEP 101 , trimmed down to only include the bits that are relevant for micro releases, a.k.a. patch, or bug fix releases. It is organized as a recipe and you can actually print this out and check items off as you complete them. How to Make A Release Here are the steps taken to make a Python release. Some steps are more fuzzy than others because there’s little that can be automated (e.g. writing the NEWS entries).

Where a step is usually performed by An Expert, the name of that expert is given. Otherwise, assume the step is done by the Release Manager (RM), the designated person performing the release. Almost every place the RM is mentioned below, this step can also be done by the BDFL of course! XXX: We should include a dependency graph to illustrate the steps that can be taken in parallel, or those that depend on other steps.

We use the following conventions in the examples below. Where a release number is given, it is of the form X.Y.MaA, e.g. 2.1.2c1 for Python 2.1.2 release candidate 1, where “a” == alpha, “b” == beta, “c” == release candidate. Final releases are tagged with “releaseXYZ” in CVS. The micro releases are made from the maintenance branch of the major release, e.g. Python 2.1.2 is made from the release21-maint branch.

Send an email to python-dev @ python . org indicating the release is about to start. Put a freeze on check ins into the maintenance branch. At this point, nobody except the RM should make any commits to the branch (or his duly assigned agents, i.e. Guido the BDFL, Fred Drake for documentation, or Thomas Heller for Windows). If the RM screwed up and some desperate last minute change to the branch is necessary, it can mean extra work for Fred and Thomas.

So try to avoid this! On the branch, change Include/patchlevel.h in two places, to reflect the new version number you’ve just created. You’ll want to change the PY_VERSION macro, and one or several of the version subpart macros just above PY_VERSION, as appropriate. Change the “%define version” line of Misc/RPM/python-2.3.spec to the same string as PY_VERSION was changed to above. E.g: % define version 2.3.1 You also probably want to reset the %define release line to ‘1pydotorg’ if it’s not already that.

If you’re changing the version number for Python (e.g. from Python 2.1.1 to Python 2.1.2), you also need to update the README file, which has a big banner at the top proclaiming its identity. Don’t do this if you’re just releasing a new alpha or beta release, but /do/ do this if you’re release a new micro, minor or major release. The LICENSE file also needs to be changed, due to several references to the release number.

As for the README file, changing these are necessary for a new micro, minor or major release. The LICENSE file contains a table that describes the legal heritage of Python; you should add an entry for the X.Y.Z release you are now making. You should update this table in the LICENSE file on the CVS trunk too. When the year changes, copyright legends need to be updated in many places, including the README and LICENSE files.

For the Windows build, additional files have to be updated. PCbuild/BUILDno.txt contains the Windows build number, see the instructions in this file how to change it. Saving the project file PCbuild/pythoncore.dsp results in a change to PCbuild/pythoncore.dsp as well. PCbuild/python20.wse sets up the Windows installer version resource (displayed when you right-click on the installer .exe and select Properties), and also contains the Python version number. (Before version 2.3.2, it was required to manually edit PC/python_nt.rc, this step is now automated by the build process.) After starting the process, the most important thing to do next is to update the Misc/NEWS file.

Thomas will need this in order to do the Windows release and he likes to stay up late. This step can be pretty tedious, so it’s best to get to it immediately after making the branch, or even before you’ve made the branch. The sooner the better (but again, watch for new checkins up until the release is made!) Add high level items new to this release. E.g. if we’re releasing 2.2a3, there must be a section at the top of the file explaining “What’s new in Python 2.2a3”.

It will be followed by a section entitled “What’s new in Python 2.2a2”. Note that you /hope/ that as developers add new features to the trunk, they’ve updated the NEWS file accordingly. You can’t be positive, so double check. If you’re a Unix weenie, it helps to verify with Thomas about changes on Windows, and Jack Jansen about changes on the Mac. This command should help you (but substitute the correct -r tag!): % cvs log - rr22a1 : | python Tools / scripts / logmerge . py > / tmp / news . txt IOW, you’re printing out all the cvs log entries from the previous release until now.

You can then troll through the news.txt file looking for interesting things to add to NEWS. Check your NEWS changes into the maintenance branch. It’s easy to forget to update the release date in this file! Check in any changes to IDLE’s NEWS.txt. Update the header in Lib/idlelib/NEWS.txt to reflect its release version and date. Update the IDLE version in Lib/idlelib/idlever.py to match. Once the release process has started, the documentation needs to be built and posted on python.org according to the instructions in PEP 101 .

Note that Fred is responsible both for merging doc changes from the trunk to the branch AND for merging any branch changes from the branch to the trunk during the cleaning up phase. Basically, if it’s in Doc/ Fred will take care of it. Thomas compiles everything with MSVC 6.0 SP5, and moves the python23.chm file into the src/chm directory. The installer executable is then generated with Wise Installation System. The installer includes the MSVC 6.0 runtime in the files MSVCRT.DLL and MSVCIRT.DLL.

It leads to disaster if these files are taken from the system directory of the machine where the installer is built, instead it must be absolutely made sure that these files come from the VCREDIST.EXE redistributable package contained in the MSVC SP5 CD. VCREDIST.EXE must be unpacked with winzip, and the Wise Installation System prompts for the directory. After building the installer, it should be opened with winzip, and the MS dlls extracted again and check for the same version number as those unpacked from VCREDIST.EXE.

Thomas uploads this file to the starship. He then sends the RM a notice which includes the location and MD5 checksum of the Windows executable. Note that Thomas’s creation of the Windows executable may generate a few more commits on the branch. Thomas will be responsible for merging Windows-specific changes from trunk to

The rest of this page is on the live site.