[python-committers] Why r69846 is not merged to "release26-maint"?
R. David Murray
rdmurray at bitdance.com
Thu Jul 2 20:56:17 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 20:56:17 CEST 2009
- Previous message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 2 Jul 2009 at 11:43, Brett Cannon wrote: > On Thu, Jul 2, 2009 at 11:42, Barry Warsaw <barry at python.org> wrote: > >> On Jul 2, 2009, at 2:29 PM, Anthony Baxter wrote: >> >> I think Barry should totally cut a completely pointless 3.0.2 release. We >>> can call it the "homage to 1.6" release. >>> >> >> We can code name it "Here Comes Another One" (guess that reference!) >> >> <god-I've-been-involved-with-python-too-long/> >>> >> >> too-much-monty-python-as-a-child-ly y'rs > > > Considering Georg just discovered Fawlty Towers I think we might need to > have required British humour training for all core committers. I can see it now...the TV and movie track at PyCon 2010, with attendance mandatory for anyone wanting to participate in the Core sprint... --David
- Previous message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list