<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Python API client_modified resolution in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Python-API-client-modified-resolution/m-p/362161#M20595</link>
    <description>&lt;P&gt;When I set the `client_modified` of the `files_upload` method in the Python API and then use `files_get_metadata` to inspect the `client_modified` attribute, I notice that the datetime.datetime object has had the microseconds set to zero. Does this mean the best resolution of the `client_modified` metadata is 1 second? This seems a bit too coarse if so. Regardless, may I ask whether the datetime is rounded to the nearest second or are the microseconds simply culled? I need to know this so I can then do comparisons. Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2019 10:34:48 GMT</pubDate>
    <dc:creator>aplowman</dc:creator>
    <dc:date>2019-09-10T10:34:48Z</dc:date>
    <item>
      <title>Python API client_modified resolution</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Python-API-client-modified-resolution/m-p/362161#M20595</link>
      <description>&lt;P&gt;When I set the `client_modified` of the `files_upload` method in the Python API and then use `files_get_metadata` to inspect the `client_modified` attribute, I notice that the datetime.datetime object has had the microseconds set to zero. Does this mean the best resolution of the `client_modified` metadata is 1 second? This seems a bit too coarse if so. Regardless, may I ask whether the datetime is rounded to the nearest second or are the microseconds simply culled? I need to know this so I can then do comparisons. Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 10:34:48 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Python-API-client-modified-resolution/m-p/362161#M20595</guid>
      <dc:creator>aplowman</dc:creator>
      <dc:date>2019-09-10T10:34:48Z</dc:date>
    </item>
    <item>
      <title>Re: Python API client_modified resolution</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Python-API-client-modified-resolution/m-p/362170#M20596</link>
      <description>&lt;P&gt;Yes, the Dropbox API itself uses&amp;nbsp;UTC datetime strings in the ISO 8601 "combined date and time representation" format, so it has a resolution of seconds, not smaller.&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="pl-pds"&gt;The Python SDK does the formatting locally to conform with the Dropbox API spec before sending it to Dropbox.&amp;nbsp;&lt;/SPAN&gt;The format string is&amp;nbsp;&lt;SPAN class="pl-pds"&gt;'&lt;/SPAN&gt;&lt;SPAN&gt;%Y-%m-&lt;/SPAN&gt;&lt;SPAN class="pl-c1"&gt;%d&lt;/SPAN&gt;&lt;SPAN&gt;T%H:%M:%SZ&lt;/SPAN&gt;&lt;SPAN class="pl-pds"&gt;', and any microseconds are just culled, not rounded.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="pl-pds"&gt;I'll pass this along as a feature request for a finer time resolution, though I can't promise if or when that might be implemented. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2019 19:22:49 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Python-API-client-modified-resolution/m-p/362170#M20596</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2019-08-27T19:22:49Z</dc:date>
    </item>
  </channel>
</rss>

