Ticket #847 (closed task: duplicate)

Opened 14 years ago

Last modified 13 years ago

csmlscan interface wishlist

Reported by: spascoe Owned by: domlowe
Priority: desirable Milestone: Reporting
Component: CSML Version:
Keywords: Cc:


This is low priority and should be considered Future CSML development

The following things would make it much easier to identify csmlscan related problems, particularly when invoking csmlscan as a module via csmlscan.main():

  • Remove calls to sys.exit() with raising an appropriate exception. This makes it possible to trap the error or invoke pdb.pm() to trace the problem.
  • Replace print statements with calls to the logging module. This allows invoking code to control what messages are displayed and where they are sent. Ideally csmlscan should send messages to it's own logger (say ndg.csmlscan) and classify log messages as ERROR, WARNING or INFO.

Change History

comment:1 Changed 14 years ago by domlowe

  • Status changed from new to assigned

Yep, csmlscan needs a lot of work before it's fully operational...!

comment:2 Changed 13 years ago by selatham

Future csml - but what umbrella will this be done under?

comment:3 Changed 13 years ago by domlowe

  • Status changed from assigned to closed
  • Resolution set to duplicate

Moved to CSML Trac  ticket:8

Note: See TracTickets for help on using tickets.