Brett Cannon writes:
> All in one is fine. Just be *very* wary of getting burned out. I
> especially would watch out for python-ideas as any random idea can end
> up there and just go on and on with no resolution.
As basically a lurker, I second that -- these summaries (and the
weekly tracke
On 4/24/07, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> Now that I should be able to actually keep up with my summary duties,
> I need to figure out how to tackle the changing landscape of the
> development lists. The old summaries were no problem, before my time.
> When the python-3000 list was c
On 4/24/07, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> So, the question I pose is how would everyone like to see this
> resolved? As I see it, there are two things I can do. I can either
> summaries each list separately, and try to sort out the cross overs.
> Or, I can start pulling in all three
On Tue, Apr 24, 2007 at 04:37:14PM -0400, Calvin Spealman wrote:
> So, the question I pose is how would everyone like to see this
> resolved? As I see it, there are two things I can do. I can either
> summaries each list separately, and try to sort out the cross overs.
> Or, I can start pulling in
Now that I should be able to actually keep up with my summary duties,
I need to figure out how to tackle the changing landscape of the
development lists. The old summaries were no problem, before my time.
When the python-3000 list was created, nearly everything was just
conceptual, floaty talk that
