I propose that Alexander Belopolsky be given svn commit access. I've
already checked with him that he's interested (he is), and I'm
prepared to mentor him while he's learning the ropes.
A brief history: Alexander's been contributing patches for almost
seven years (I think http://bugs.python.org/issue798269 is the first);
in that time he's provided numerous patches, comments, and patch
reviews. Just as a guide, a quick search on bugs.python.org shows
that he's nosy on over 200 issues. I've recently worked closely with
him on a couple of patches, and think he's ready for commit rights.
In particular, I think it would be great to have his help with the
datetime module, which is in currently need of some care and
Any objections or comments?
Following discussion on python-dev, I plan to untabify the C codebase
this afternoon. It would probably be better if nobody modified any C files
in the meantime (except those that already use 4 space indents).
I expect the whole operation to take a couple of hours.
I'm preparing the argparse module for the 2.7 and 3.2 branches. Could
someone remind me again what the commit process is? Commit to 2.7 and
merge to 3.2? And do we merge with svnmerge.py or svn merge? There's
probably a webpage explaining this somewhere, but my Google-fu is
failing me right now.
Where did you get that preposterous hypothesis?
Did Steve tell you that?
--- The Hiphopopotamus