Opened 16 years ago
Closed 15 years ago
#119 closed defect (invalid)
AttributeError: 'module' object has no attribute 'DEBUG'
Reported by: | stodge | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | logging | Version: | 0.3.0 |
Keywords: | Cc: |
Description
I copy/pasted the complete client and server examples from http://foolscap.lothar.com/docs/using-foolscap.html#auto6 and ran them on Python 2.5.2 on WinXP but I get an error:
Traceback (most recent call last): File "C:\Documents and Settings\stodge\workspace\remote_test\src\tub_server1.py", line 2, in <module> from foolscap import Referenceable, UnauthenticatedTub File "C:\Python25\Lib\site-packages\foolscap\__init__.py", line 6, in <module> from foolscap.pb import Tub, UnauthenticatedTub, getRemoteURL_TCP File "C:\Python25\Lib\site-packages\foolscap\pb.py", line 9, in <module> from foolscap import ipb, base32, negotiate, broker, observer, eventual, storage File "C:\Python25\Lib\site-packages\foolscap\negotiate.py", line 7, in <module> from foolscap import broker, referenceable, vocab File "C:\Python25\Lib\site-packages\foolscap\broker.py", line 15, in <module> from foolscap import call, slicer, referenceable, copyable, remoteinterface File "C:\Python25\Lib\site-packages\foolscap\call.py", line 11, in <module> from foolscap.logging import log File "C:\Python25\Lib\site-packages\foolscap\logging\log.py", line 9, in <module> from foolscap.logging.incident import IncidentQualifier, IncidentReporter File "C:\Python25\Lib\site-packages\foolscap\logging\incident.py", line 7, in <module> from foolscap.logging import levels, app_versions File "C:\Python25\Lib\site-packages\foolscap\logging\levels.py", line 3, in <module> NOISY = logging.DEBUG # 10 AttributeError: 'module' object has no attribute 'DEBUG'
Does foolscap support this version of Python/platform?
Thanks
Change History (2)
comment:1 Changed 16 years ago by
Component: | unknown → logging |
---|
comment:2 Changed 15 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
Lacking further information, and given that python2.5's logging module does seem to have a DEBUG symbol, I'm going to close this one as unreproducible. stodge: if you're still seeing this problem, please feel free to re-open this ticket.
Note: See
TracTickets for help on using
tickets.
I haven't tested it explicitly, but I think it ought to support that platform.
It looks a little bit like the "logging" module that we're importing is getting the wrong module. If you start a python shell (just run "python" with no arguments), and do "import logging" and "dir(logging)", what do you get?
Maybe there's some other logging.py that's sitting around on your PYTHONPATH which is getting in the way..