time interval incorrectly parsed

Bug #1009685 reported by Thomas Girard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TelecomLogServiceClient
Fix Released
High
Thomas Girard

Bug Description

Stacktrace follows:

Traceback (most recent call last):
  File "./tlscli", line 686, in <module>
    print logfactory.get(long(i))
  File "./tlscli", line 177, in new_f
    return f(*args, **kwds)
  File "./tlscli", line 520, in __str__
    self.interval(),
  File "./tlscli", line 177, in new_f
    return f(*args, **kwds)
  File "./tlscli", line 461, in interval
    Log._stop_time(interval.stop))
  File "./tlscli", line 455, in _stop_time
    return Log._str_to_time(date)
  File "./tlscli", line 431, in _str_to_time
    dt = dateutil.parser.parse(date)
  File "/usr/lib/python2.7/dist-packages/dateutil/parser.py", line 697, in parse
    return DEFAULTPARSER.parse(timestr, **kwargs)
  File "/usr/lib/python2.7/dist-packages/dateutil/parser.py", line 301, in parse
    res = self._parse(timestr, **kwargs)
  File "/usr/lib/python2.7/dist-packages/dateutil/parser.py", line 349, in _parse
    l = _timelex.split(timestr)
  File "/usr/lib/python2.7/dist-packages/dateutil/parser.py", line 143, in split
    return list(cls(s))
  File "/usr/lib/python2.7/dist-packages/dateutil/parser.py", line 137, in next
    token = self.get_token()
  File "/usr/lib/python2.7/dist-packages/dateutil/parser.py", line 68, in get_token
    nextchar = self.instream.read(1)
AttributeError: 'long' object has no attribute 'read'

Changed in tlscli:
status: New → In Progress
assignee: nobody → Thomas Girard (teejeejee-oss)
Changed in tlscli:
status: In Progress → Fix Committed
Changed in tlscli:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.