Hi Mike,
It would probably be easy to implement this sort of logger -- you can
look at rospy.impl.rosout for the relevant places you would probably
plug into. I think it would be a useful alternative to the current
rospy.log* design as it keeps rospy calls out of lower-level
libraries.
One of these days I want to overhaul how rospy logging is done and
would appreciate any recommendations. I've been looking at logging
alternatives like logbook [1] for inspiration -- the logbook link
also summarizes some of the reasons why I've found binding on top of
logging problematic from a design perspective.
- Ken
[1]:
http://www.scribd.com/doc/37071444/Logbook
On Thu, Sep 16, 2010 at 7:20 AM, Mike Purvis
<
mpurvis@clearpathrobotics.com> wrote:
> Hey,
> I have a question about logging and rospy. We've been using stdout, but with
> doing more remote node launches, it's advantageous to use the rospy.log*
> functions which put Log messages on the /rosout topic.
> One of our main nodes is a light ROS wrapper over a more general-purpose
> serial Python API to our hardware. This Python API already produces
> extensive debug and logging information using the standard python
> logging.getLogger facility. Is there an easy way to expose this information
> on rosout? I took a quick look here and didn't see anything--- has anyone
> written a log handler that captures standard python log messages and sends
> them as Ros Log messages?
> What I'm envisioning is something like this:
> logging.getLogger('clearpath.horizon').addHandler(RosLogHandler())
> Does this exist? If not, is there a reason not to do such a thing?
> Thanks,
> Mike
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
(text/plain)