Tom Kuiper added the comment:
On 10/30/2012 05:29 PM, R. David Murray wrote:
> R. David Murray added the comment:
>
> Do none of those submodules import logging?
>
> It is unlikely that this is a Python bug. Somewhere _fmt is getting set to
> an integer. The way to pro
Tom Kuiper added the comment:
Give me a few moments to dig further. I may have found the submodule
culprit. Checking.
Tom
On 10/30/2012 05:29 PM, R. David Murray wrote:
> R. David Murray added the comment:
>
> Do none of those submodules import logging?
>
> It is unlikely
New submission from Tom Kuiper:
This error comes from the logging module when a message is logged, but only
when I also import another module which does use logging at all:
Traceback (most recent call last):
File "/usr/lib/python2.6/logging/__init__.py", line 776, in em
Tom Kuiper added the comment:
Do I have to do that? I've never used the Python bug tracking system
before.
> BTW: I'm happy you solved this bug.
>
I guess we could consume a few beers over whether it's a bug or not.
Cheers
Tom
--
_
Tom Kuiper added the comment:
That's a good point, Marco. I'd forgotten about the distinction.
Converting 'filename' to a Python string with 'str()' fixed the problem.
> However, when I tried to run your example, newWF.py, and tried to open a
New submission from Tom Kuiper :
Normal behavior:
>>> from os import path
>>> filename
=
"/home/kuiper/Projects/microdischarges/Observing/2009-09-01/STATS_NP2000_VSR1A.1W1.09-244-193632"
>>> print filename
/home/kuiper/Projects/microdischarges/Observing/200
