[New-bugs-announce] [issue7014] Logging incompatible with IronPython

Michael Foord report at bugs.python.org
Mon Sep 28 22:53:00 CEST 2009


New submission from Michael Foord <michael at voidspace.org.uk>:

Logging is incompatible with IronPython 2.6. 

See: http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=24714

The core of the issue is that logging assumes that if sys._getframe is
not defined then frames can still be accessed through exceptions.

For IronPython this isn't true - *if* sys._getframe is not available in
IronPython (frames have to be specifically enabled) then frames are not
available at all.

Are there any platforms now where sys._getframe will be unavailable but
frames are still available? I don't think this applies to Jython where
frames are always available in recent versions (2.5 - and this would
only be backported to 2.6).

----------
assignee: michael.foord
components: Library (Lib)
messages: 93233
nosy: michael.foord, vinay.sajip
severity: normal
stage: needs patch
status: open
title: Logging incompatible with IronPython
type: crash
versions: Python 2.6, Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7014>
_______________________________________


More information about the New-bugs-announce mailing list