[Python-Dev] sys.settrace: behavior doesn't match docs (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon May 2 15:12:32 CEST 2011
- Previous message: [Python-Dev] sys.settrace: behavior doesn't match docs
- Next message: [Python-Dev] 2to3 status, repositories and HACKING guide
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, May 2, 2011 at 10:47 PM, Mark Hammond <mhammond at skippinet.com.au> wrote:
On 2/05/2011 9:27 PM, Ned Batchelder wrote: ...
Maybe the fact no one noticed the docs were wrong proves that no one ever tried returning None from a local trace function. Or if they did, they should have complained by now. IMO, if the behaviour regresses from how it is documented and how it previously worked and no reports of the regression exist, we should just fix it without regard to people relying on the "new" functionality...
+1
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] sys.settrace: behavior doesn't match docs
- Next message: [Python-Dev] 2to3 status, repositories and HACKING guide
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]