incorrect display of Timestamp where sub second portion has leading zeros

[rbinnun]

When querying HBASE using jaydebeapi from python 3.6 I'm pulling DBAPITypeObject('TIMESTAMP') objects and finding that when the sub second portion of the time has leading zeros they get concatenated, e.g., 2017-06-19 15:30:00.096965169 ends up showing as 2017-06-19 15:30:00.960000 Specifically, Why is the 0.096 turning into 0.96

Is this a known issue? any workarounds?

[jpsteege]

Also addressed in issue 175, with a patch + merge request attached.