[Python-Dev] What should we do with cProfile? (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Wed May 30 05:30:33 CEST 2012
- Previous message: [Python-Dev] What should we do with cProfile?
- Next message: [Python-Dev] [Python-checkins] cpython: Issue #14744: Use the new _PyUnicodeWriter internal API to speed up str%args
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 30, 2012 at 1:01 PM, Eli Bendersky <eliben at gmail.com> wrote:
And as Steven said, the 3.3 timeline doesn't have anything really special about it. Although there's still time until the beta release, even if this is done for 3.4 it will be great.
Yep - there's a reason the 3.4 target gets added to the tracker even before 3.3 is out. It's precisely so we can bump things as soon as we reach a point where we're comparing the effort we think is needed to get them agreed on and/or bedded down properly and the time remaining before the first beta and officially say "not going to happen".
I've already done that for Eugene Toder's proposed compiler enhancements. It's a promising approach, but it's way too late in the 3.3 cycle to be contemplating that kind of change.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] What should we do with cProfile?
- Next message: [Python-Dev] [Python-checkins] cpython: Issue #14744: Use the new _PyUnicodeWriter internal API to speed up str%args
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]