[issue5287] logging package on IronPython

2009-02-19 Thread Vinay Sajip
Vinay Sajip added the comment: Fixes checked into trunk & py3k. -- resolution: accepted -> fixed status: open -> closed ___ Python tracker ___ ___

[issue5287] logging package on IronPython

2009-02-18 Thread Vinay Sajip
Vinay Sajip added the comment: I know - I just thought 2.6 was the priority for Michael, so I checked that in first, then got sidetracked...I'll get on it shortly. I should have left the issue as "Open" to remind me - correcting that now. -- resolution: fixed -> accepted status: closed

[issue5287] logging package on IronPython

2009-02-17 Thread Antoine Pitrou
Antoine Pitrou added the comment: Vinay, the fix should also be committed to trunk (unless the relevant code doesn't exist anymore), and to py3k. ___ Python tracker ___ __

[issue5287] logging package on IronPython

2009-02-17 Thread Vinay Sajip
Vinay Sajip added the comment: Fix checked into release26-maint. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue5287] logging package on IronPython

2009-02-17 Thread Michael Foord
Michael Foord added the comment: Attached is an alternative patch that wraps the call to findCaller in a try:...except. Added file: http://bugs.python.org/file13116/logging2.patch ___ Python tracker ___

[issue5287] logging package on IronPython

2009-02-17 Thread Michael Foord
Michael Foord added the comment: @Victor IronPython doesn't use Python stack frames, so tracking them and then constructing the objects on demand would add about a ~10% performance hit to IronPython. Even when it is done it is likely to be an option rather than on by default - using _getframe is

[issue5287] logging package on IronPython

2009-02-17 Thread STINNER Victor
STINNER Victor added the comment: > IronPython provides sys._getframe but it throws an exception > if you call it with a non-zero depth. Stupid question: why not fixing sys._getframe()? -- nosy: +haypo ___ Python tracker

[issue5287] logging package on IronPython

2009-02-17 Thread Antoine Pitrou
Antoine Pitrou added the comment: Rather than explicit testing for sys.platform, a try...except would be more flexible and more future-proof. -- nosy: +pitrou ___ Python tracker

[issue5287] logging package on IronPython

2009-02-16 Thread Benjamin Peterson
Changes by Benjamin Peterson : -- assignee: -> vsajip nosy: +vsajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri