Hi,
Great, thanks Russell! I started the changes to logging to read the
machine,port, and filename from a Policy file. But ran out of time to
finish getting it working. I will hand that over to Jonathan Myers. But
it will be a management priority call about what we need for DC1
functionality.
Cheers,
Michelle
On Tue, 8 Aug 2006, Russell E Owen wrote:
I made a few minor tweaks to the new logging module:
- Added named constants for the priority argument. I strongly suggest using
these instead of strings because spelling errors are caught sooner and more
reliably.
- Made the 3rd argument to log() optional.
- The log function and named constants are now imported into the module's
namespace.
- Updated the API doc accordingly.
- Tweaked a few things so logReceiver.py is correctly installed as a
command-line script.
Example of use:
import lsst.mw.dps.pipeexec.logging as log
log.log("this is a debug message", log.DEBUG)
Other known issues (that I made no attempt to address):
- The logging server and port are hard-coded. In the long run that needs to
be more flexible, but can live with hard-coding for DC1?
- Michelle reported some duplicate messages.
Regards,
-- Russell
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
