Issue 7014: Logging incompatible with IronPython (original) (raw)

Issue7014

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/51263

classification

process

Created on 2009-09-28 20:52 by michael.foord, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg93233 - (view)	Author: Michael Foord (michael.foord) *	Date: 2009-09-28 20:52
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).
msg93256 - (view)	Author: Vinay Sajip (vinay.sajip) *	Date: 2009-09-29 07:19
Fix checked into trunk and release26-maint. Please verify. Note - the problem is not just to do with availability of sys._getframe in Python - it's actually because sys.exc_traceback.tb_frame.f_back is None (even though sys.exc_traceback.tb_frame is a frame object) when -X:Frames is not specified with IronPython. The "fix" in CodePlex work item 24714 would be suboptimal, because frame information would be unavailable even if -X:Frames were to be specified.
msg93307 - (view)	Author: Michael Foord (michael.foord) *	Date: 2009-09-29 17:47
Works for me - thanks Vinay.