[python-committers] Cutting Python 2.6
Benjamin Peterson
musiccomposition at gmail.com
Fri Oct 3 22:55:22 CEST 2008
More information about the python-committers mailing list
Fri Oct 3 22:55:22 CEST 2008
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Oct 3, 2008 at 7:09 AM, Barry Warsaw <barry at python.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Oct 3, 2008, at 12:34 AM, Anthony Baxter wrote: > >> It's happened a couple of times when I've made releases - the process >> I had was to automate it as much as possible, then take the generated >> tarball, unpack it freshly and run the full tests, and then check >> things like the README and all those other places. Making a release is >> still a pretty fiddly process, and things slip through. > > Anthony's spot on. Even with a release script and PEP 101, it's still > pretty labor intensive. Of course, Python 2.7 and 3.1 still have no > official RM <wink> so if you want firsthand experience, the opportunity is > available. I would actually be interested in this. However, I still am quite inexperienced and gladly step aside for anyone who's been around longer. -- Cheers, Benjamin Peterson "There's nothing quite as beautiful as an oboe... except a chicken stuck in a vacuum cleaner."
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list