Logging module: problem with some mapping keys

[Tekkaman]

I'm getting a strange behaviour from the "pathname" and "lineno"
formatter mapping keys. Instead of my file and my line number I get:

/usr/lib/python2.4/logging/__init__.py

as the file, and 1072 as the line number. I set up my config as
follows:

logBaseConf = {
'level' : logging.DEBUG,
'format' : "%(levelnam e)-8s|%(asctime)s| %(pathname)s,
%(name)s, line %(lineno)s|%(me ssage)s",
'datefmt ': '%d %b %Y, %H:%M:%S',
'filename': 'logtest.log',
'filemode': 'a'
}
logging.basicCo nfig(**logBaseC onf)

I'm not using any executable-generating tools such as cx_Freeze or
Psyco. In fact, I'm getting this error on a very basic script with the
specific purpose of testing the logging module capabilities.

Thanks in advance for any contribution.

T.

[sim.sim]

Hi, i've check documentation, and found that logging.basicCo nfig takes
no arguments (probably we have different versions of logging package),
and i've never used it.

just try this:
fileName = 'testlog.log'
logName = 'LOG'
iHandler = logging.FileHan dler(fileName)
iHandler.setFor matter(
logging.Formatt er("%(levelname )-8s|%(asctime)s| %(pathname)s,%( name)s,
line %(lineno)s|%(me ssage)s") )

iLog = logging.getLogg er(logName)
iLog.addHandler (iHandler)
iLog.setLevel(l ogging.DEBUG)

iLog.info('hell o logging')

it gives me:

INFO |2006-12-13 19:57:33,575|te st.py,LOG, line 12|hello logging
On 13 Dec., 19:02, "Tekkaman" <simone....@gma il.comwrote:

I'm getting a strange behaviour from the "pathname" and "lineno"
formatter mapping keys. Instead of my file and my line number I get:

/usr/lib/python2.4/logging/__init__.py

as the file, and 1072 as the line number. I set up my config as
follows:

logBaseConf = {
'level' : logging.DEBUG,
'format' : "%(levelnam e)-8s|%(asctime)s| %(pathname)s,
%(name)s, line %(lineno)s|%(me ssage)s",
'datefmt ': '%d %b %Y, %H:%M:%S',
'filename': 'logtest.log',
'filemode': 'a'
}
logging.basicCo nfig(**logBaseC onf)

I'm not using any executable-generating tools such as cx_Freeze or
Psyco. In fact, I'm getting this error on a very basic script with the
specific purpose of testing the logging module capabilities.

Thanks in advance for any contribution.

T.

--
Maksim Kasimov

[Peter Otten]

Tekkaman wrote:

I'm getting a strange behaviour from the "pathname" and "lineno"
formatter mapping keys. Instead of my file and my line number I get:

/usr/lib/python2.4/logging/__init__.py

as the file, and 1072 as the line number. I set up my config as
follows:

logBaseConf = {
'level' : logging.DEBUG,
'format' : "%(levelnam e)-8s|%(asctime)s| %(pathname)s,
%(name)s, line %(lineno)s|%(me ssage)s",
'datefmt ': '%d %b %Y, %H:%M:%S',
'filename': 'logtest.log',
'filemode': 'a'
}
logging.basicCo nfig(**logBaseC onf)

I'm not using any executable-generating tools such as cx_Freeze or
Psyco. In fact, I'm getting this error on a very basic script with the
specific purpose of testing the logging module capabilities.

Thanks in advance for any contribution.

An evil symlink, maybe?

$ ln -s /usr/local/lib/python2.4/logging
$ python
[snip]

>>import logging
logging.basic Config(format=" %(pathname)s")
logging.getLo gger().critical ("yadda")

/usr/local/lib/python2.4/logging/__init__.py

>>>

$ rm logging
$ python
[snip]

>>import logging
logging.basic Config(format=" %(pathname)s")
logging.getLo gger().critical ("yadda")

<stdin>

Peter

[Tekkaman]

sim.sim wrote:

Hi, i've check documentation, and found that logging.basicCo nfig takes
no arguments (probably we have different versions of logging package),

Your Python version is < 2.4. Now basicConfig takes optional keyword
args:

basicConfig([**kwargs])
Does basic configuration for the logging system by creating a
StreamHandler with a default Formatter and adding it to the root
logger. The functions debug(), info(), warning(), error() and
critical() will call basicConfig() automatically if no handlers are
defined for the root logger.

In my real application (not the small test script!) This behaviour is
very useful since I can call basicConfig only once in the main file and
then all I have to do in the other files is:

import logging
self.logger = logging.getLogg er("myClass")

Everything works smoothly except for not being able to get file and
line number info.

and i've never used it.

just try this:
fileName = 'testlog.log'
logName = 'LOG'
iHandler = logging.FileHan dler(fileName)
iHandler.setFor matter(
logging.Formatt er("%(levelname )-8s|%(asctime)s| %(pathname)s,%( name)s,
line %(lineno)s|%(me ssage)s") )

iLog = logging.getLogg er(logName)
iLog.addHandler (iHandler)
iLog.setLevel(l ogging.DEBUG)

iLog.info('hell o logging')

it gives me:

INFO |2006-12-13 19:57:33,575|te st.py,LOG, line 12|hello logging
On 13 Dec., 19:02, "Tekkaman" <simone....@gma il.comwrote:

I'm getting a strange behaviour from the "pathname" and "lineno"
formatter mapping keys. Instead of my file and my line number I get:

/usr/lib/python2.4/logging/__init__.py

as the file, and 1072 as the line number. I set up my config as
follows:

logBaseConf = {
'level' : logging.DEBUG,
'format' : "%(levelnam e)-8s|%(asctime)s| %(pathname)s,
%(name)s, line %(lineno)s|%(me ssage)s",
'datefmt ': '%d %b %Y, %H:%M:%S',
'filename': 'logtest.log',
'filemode': 'a'
}
logging.basicCo nfig(**logBaseC onf)

I'm not using any executable-generating tools such as cx_Freeze or
Psyco. In fact, I'm getting this error on a very basic script with the
specific purpose of testing the logging module capabilities.

Thanks in advance for any contribution.

T.

--
Maksim Kasimov

[Tekkaman]

Peter Otten wrote:

>
An evil symlink, maybe?

Thanks for the hint, but it's not a symlink

>
$ ln -s /usr/local/lib/python2.4/logging
$ python
[snip]

>import logging
logging.basicC onfig(format="% (pathname)s")
logging.getLog ger().critical( "yadda")

/usr/local/lib/python2.4/logging/__init__.py

>>

$ rm logging
$ python
[snip]

>import logging
logging.basicC onfig(format="% (pathname)s")
logging.getLog ger().critical( "yadda")

<stdin>

Peter

[Peter Otten]

Tekkaman wrote:

Thanks for the hint, but it's not a symlink

What does logging._srcfil e contain? Should be

>>import logging
logging._srcf ile

'/usr/lib/python2.4/logging/__init__.py'

on your machine, but probably isn't.

Peter

[Tekkaman]

'/usr/lib64/python2.4/logging/__init__.py'

Peter Otten wrote:

Tekkaman wrote:

Thanks for the hint, but it's not a symlink

What does logging._srcfil e contain? Should be

>import logging
logging._srcfi le

'/usr/lib/python2.4/logging/__init__.py'

on your machine, but probably isn't.

Peter

[Peter Otten]

Tekkaman wrote:

Peter Otten wrote:

>Tekkaman wrote:

Thanks for the hint, but it's not a symlink

What does logging._srcfil e contain? Should be

>>import logging
logging._srcf ile

'/usr/lib/python2.4/logging/__init__.py'

on your machine, but probably isn't.

'/usr/lib64/python2.4/logging/__init__.py'

And neither /usr/lib nor /usr/lib/python2.4 are symlinks?

Peter

PS: Please don't top-post

[Tekkaman]

lib is a symlink to lib64

Peter Otten wrote:

Tekkaman wrote:

Peter Otten wrote:

Tekkaman wrote:

Thanks for the hint, but it's not a symlink

What does logging._srcfil e contain? Should be

import logging
logging._srcfi le
'/usr/lib/python2.4/logging/__init__.py'

on your machine, but probably isn't.

'/usr/lib64/python2.4/logging/__init__.py'

And neither /usr/lib nor /usr/lib/python2.4 are symlinks?

Peter

PS: Please don't top-post

[Tekkaman]

Peter Otten wrote:

Tekkaman wrote:

Peter Otten wrote:

Tekkaman wrote:

Thanks for the hint, but it's not a symlink

What does logging._srcfil e contain? Should be

import logging
logging._srcfi le
'/usr/lib/python2.4/logging/__init__.py'

on your machine, but probably isn't.

'/usr/lib64/python2.4/logging/__init__.py'

And neither /usr/lib nor /usr/lib/python2.4 are symlinks?

Peter

PS: Please don't top-post

Sry for the top-post, I noticed the PS a moment too late!