On Jan 21, 2010, at 02:45 PM, R. David Murray wrote: >I've looked briefly at your email6 branch, and will take a look at >the others. But unless you think there are specifically relevant >bits to look at, I probably won't look too closely until we have >the new API design roughed out. > >Did you start doing any test refactoring in any of the branches?
I did, but honestly it's been so long since I hacked on these branches, I don't remember what's in them. :/ email6 has I think the latest changes aligned to my thinking about API improvements and probably also includes some test refactoring email-ng is just the email package and contains some header module refactoring and a start on doctests for headers. The nice thing about using more doctests is that it can serve as the basis for improved documentation. 30email has some additional refactoring (that might be similar to what's in email6) along with the results of work done at last year's pycon. I'm sorry that it's so disorganized, but you seem to be pretty good at untangling nasty knots. :) Probably best to start with email6 and then just review the top few revisions in the other branches to see if there's anything useful in them. >> I'm in the process of re-establishing code imports of the various >> Python branches on Launchpad. They had been using the bzr mirrors on >> code.python.org, but those haven't been updated in a very long time. >> I'm going to blow those away and re-import from the Subversion >> branches. After that's working it should allow you to bzr branch any >> active Python branch and hack on things from there. That might make >> the most sense since some of the bugs you've identified affect other >> than just the email package. > >I think since you are the email czar and you are deeply involved with >bzr and launchpad, that this makes sense :) Yay! :) >I'm not sure how best to integrate this with Launchpad to make it public, >though. I created a project (python-email6), pulled py3k according to >your instructions on python-dev, pushed it to launchpad, and linked it >to to the project as trunk. Was that the right thing to do? Or should >I request membership in the Python team and create an 'email6' branch >there instead? What you did isn't too bad actually. Whether it was the right thing to do depends on how we want to manage commit access to the email branch. I see no problem adding you to the ~python-dev team on Launchpad and creating the branch in the python project. That just means everyone in ~python-dev could commit to the branch (by default). I'd have no problem with that. Alternatively, we'd need to create a team for the python-email6 project so that folks other than just you have commit access to the branch. It's only a little more work that way, just because it's more things to set up, but it's not that big of a deal. So the question is: how locked down do you want to make this branch, and are there folks who would like to commit to this branch that shouldn't be added to ~python-dev? Either way, we have to remember to occasionally merge the py3k branch back into our branch so as to keep up on changes there. >> >I'm also interested to know who will be at PyCon and interested in BOF >> >and/or sprint activities involving the email package. >> >> I'll be at PyCon though I don't yet know exactly what I'll be sprinting on. >> email package is a possibility. The sprint sign up page is here: >> >> http://us.pycon.org/2010/sprints/signup/ > >The sprint page doesn't list the core sprint yet. Any idea who is >organizing it this year? It might be me, but I'm not sure :). I think Brett is not going to attend the sprints so I'm slated to give the intro-to-sprinting talk. I'm not sure if that also means I've "volunteered" to organize the core sprint or not. I'll try to figure that out. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Email-SIG mailing list Email-SIG@python.org Your options: http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com
