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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.5
• Fix Version/s: proton-0.6
• Component/s: proton-c
• Assignee: Ken Giusti
• Reporter: Ken Giusti
• Created: 06/Dec/13 16:14
• Updated: 07/Jan/16 11:34
• Resolved: 09/Dec/13 18:45

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.