"AB" == Anthony Baxter
writes:
AB> [resend: sorry if you see it twice, but I can't see that the AB> original ever got through...] AB> Ok, I'd like to make the 2.1.2 release some time in the first AB> half of the week starting 7th Jan, assuming that's ok for the AB> folks who'll need to do the work on the PC/Mac packaging. One of the things I'd really like to be sure works in 2.1.2 is largefile support. I've had some trouble along these lines on filesystems that I know have largefile (because a Python 2.2 built on the same platform works fine). Do we expect that largefile support should work in Python 2.1.2? I'm okay that autoconf detection fails as long as the instructions in the posix module work: http://www.python.org/doc/current/lib/posix-large-files.html I've had some failures on 2.4.7 kernels w/ ext3 filesystems. AB> I notice that pep 101 is pretty strongly focussed on the major AB> releases, not the minor ones. Is it worth making a modified AB> version of this PEP with the minor release steps? I'd be more inclined to clone PEP 101 into a PEP 102 with micro release instructions. The nice thing about 101 is that you can just go down the list, checking things off in a linear fashion as you complete each item. I'd be loathe to break up the linearity of that. AB> I don't have access to creosote.python.org, so someone else's AB> going to need to do this. I can certainly help with any fiddling necessary on creosote. Then again... AB> As far as 2.2.1 goes, I'm happy to keep on the patch czar AB> role. ...if this is going to be a recurring role, we might just want to give you access to the web cvs tree and creosote. AB> Is trying for a release before the conference too AB> aggressive a timeframe? There seem to be a number of niggles AB> that'd be nice to have fixed... Hey, if you're up for it! dunno-about-you-but-i'm-planning-a-vacation-ly y'rs, -Barry