code: def _update(self, response_headers):
          
  
          if 'x-ratelimit-remaining' not in response_headers:
              # This could be because the API returned an error response, or it
              # could be because we're using something like read-only credentials
              # which Reddit doesn't appear to care about rate limiting.
              return
  
          self.used = float(response_headers['x-ratelimit-used'])
          self.remaining = float(response_headers['x-ratelimit-remaining'])
          self.seconds_to_reset = int(response_headers['x-ratelimit-reset'])
          _logger.debug('Rate limit: %s used, %s remaining, %s reset',
                        self.used, self.remaining, self.seconds_to_reset)
  
          if self.remaining <= 0:
              self.next_request_timestamp = time.time() + self.seconds_to_reset
          else:
              self.next_request_timestamp = None
docs: Update the state of the rate limiter based on the response headers:
  
              X-Ratelimit-Used: Approximate number of requests used this period
              X-Ratelimit-Remaining: Approximate number of requests left to use
              X-Ratelimit-Reset: Approximate number of seconds to end of period
  
          PRAW 5's rate limiting logic is structured for making hundreds of
          evenly-spaced API requests, which makes sense for running something
          like a bot or crawler.
  
          This handler's logic, on the other hand, is geared more towards
          interactive usage. It allows for short, sporadic bursts of requests.
          The assumption is that actual users browsing reddit shouldn't ever be
          in danger of hitting the rate limit. If they do hit the limit, they
          will be cutoff until the period resets.