Michael Foord wrote: > Hello all, > > Issue 5287 is a patch for the logging module for compatibility with > IronPython. IronPython provides sys._getframe but it throws an exception > if you call it with a non-zero depth. This may be fixed in a future > version of IronPython. > > http://bugs.python.org/issue5287 > > It doesn't at all change the behaviour on other platforms (does an > explicit platform check I'm afraid) but fixes a nasty problem with the > logging module not working at all on IronPython. As this is a bugfix for > IronPython at least and IronPython 2.6 is currently being worked on > (tracking Python 2.6) it would be great to get this into 2.6-maint. I've submitted an alternative patch that catches the error _getframe raises on IronPython. As it is possible that _getframe will work on IronPython in the future (although it is likely to be enabled by a switch as tracking Python frames has a performance cost) this is a slightly more future proof solution. Michael > > All the best, > > Michael > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4