Message timestamp format change?

Issue #84 new
Mike Molt created an issue

Did something change such that when you pass decimal time to the Message timestamp, it adds "Timestamp" as a prefix?

Comments (6)

  1. Travis Travelstead

    Personally I would avoid the str representation of the message except for debugging purposes. Use the attribute directly to get the float value in the most efficient and accurate way.

  2. Brian Thorne repo owner

    Mike is this the can_logger output that has changed - or your own program?

    I agree with Travis though, avoid parsing the str repr and instead define your own message format function which displays exactly what you want.

  3. Mike Molt reporter

    Thanks guys. Yes, this is a program of my own. I didn't use it for a while, and yesterday when I ran it, it crashed (on a new Raspberry PI, with what was obviously an updated version of python-can)...and so I traced it down to the addition of the descriptions in the Message.

    I'll move away from the str repr, and just look at the message attributes now.

    However, I'm curious, what drove the need to put the descriptions in the str representation of the Message? Why don't all the elements of the str rep have descriptions?

  4. Mike Molt reporter

    Looks like the listener/buffered reader utilizes the str repr of the can message...is this true?

  5. Log in to comment