Set logging to capture warnings (Trac #324)

[ajj]

Set logging to use logging.capturewarnings(True)

Migrated from http://trac.sasview.org/ticket/324

{
    "status": "closed",
    "changetime": "2015-03-20T20:19:58",
    "_ts": "2015-03-20 20:19:58.885965+00:00",
    "description": "Set logging to use logging.capturewarnings(True)",
    "reporter": "ajj",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasView QA and testing",
    "time": "2015-02-14T16:24:12",
    "component": "SasView",
    "summary": "Set logging to capture warnings",
    "priority": "major",
    "keywords": "",
    "milestone": "SasView 3.1.0",
    "owner": "",
    "type": "defect"
}

[butlerpd]

Trac update at 2015/03/10 14:49:05: butler commented:

Not critical... could be moved to 4 if we dont' have time

[pkienzle]

Trac update at 2015/03/10 15:51:21: pkienzle commented:

After logging.basicConfig in sasview/sasview.py, line 15.

[sasview-bot]

Trac update at 2015/03/19 14:01:06: krzywon commented:

I added this in my latest push and tested it using warning instead of info in places. The warnings are now captured and sent to the console log. I think we might also want to have anything that goes into the console log get output into the sasview.log file for the users records. I am leaving the ticket open for now until we decide whether or not we should do this.

[sasview-bot]

Trac update at 2015/03/20 20:19:58:

• krzywon commented:

Errors and warnings that are posted to the console log are now also added to the sasview.log file. Status messages (e.g. "INFO: Fitting complete!") are not to limit the size of the file.

• krzywon changed resolution from "" to "fixed"
• krzywon changed status from "new" to "closed"