Seo Sanghyeon wrote:
2008/12/2 Deepali Abhyankar [EMAIL PROTECTED]:
(logging and _getframe)
Please suggest solution to resolve this
https://fepy.svn.sourceforge.net/svnroot/fepy/trunk/patches/stdlib/2.4.4/patch-stdlib-logging-getframe
Seo - you're still alive! How about an
2008/12/2 Deepali Abhyankar [EMAIL PROTECTED]:
(logging and _getframe)
Please suggest solution to resolve this
https://fepy.svn.sourceforge.net/svnroot/fepy/trunk/patches/stdlib/2.4.4/patch-stdlib-logging-getframe
--
Seo Sanghyeon
___
Users mailing
Hello Deepali,
sys._getframe is not available in IronPython. If you post the relevant
section of code from the logging module we may be able to suggest a
patch / workaround (disabling some functionality may be the way forward
- but often getframe is used to find a trivial bit of information
Hi
I am using Iron Python 2.0 release candidate 2.
I am using logging module
Code is:
Import logging
logger = logging.getLogger(Trial)
logger.setLevel(logging.INFO)
hdlr = logging.FileHandler(data.txt,w)
hdlr.setLevel(logging.INFO)
formatter =
Seo:
Yes, please, make a new release as soon as you can. I have uploaded the
IPy-compatible version of adodbapi to the trunk, and it needs 2.0 to work
correctly. The 2.0 installer from MS is nice, but the batteries included
version from FePy will be nicer.
--
Vernon
On Tue, Dec 2, 2008 at 6:01
Message-
From: Seo Sanghyeon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2008 6:27 PM
To: [EMAIL PROTECTED]; Discussion of IronPython
Subject: Re: [IronPython] Logging module error
2008/12/2 Deepali Abhyankar [EMAIL PROTECTED]:
(logging and _getframe)
Please suggest solution