Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-475

[python] Proton wrapper API's use of time values is inconsistent

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.5
    • Fix Version/s: 0.6
    • Component/s: proton-c
    • Labels:
      None

      Description

      The precision used for timeout values in the Python API is inconsistent. In some case (messenger's timeout for example), timeouts are expressed in seconds using a float. In other cases, (driver wait(), etc), timeouts are expressed in milliseconds.

      To be consistent with the Python time module, we should be expressing timeout values as seconds using a float.

      There should be no change to the AMQP timestamp type, of course, which is defined as milliseconds since unix epoch.

        Attachments

          Activity

            People

            • Assignee:
              kgiusti Ken Giusti
              Reporter:
              kgiusti Ken Giusti
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: