comparing datetime to int in ticket/query.py

[intgr@…]

Sorry about the bad paste.

TypeError: can't compare datetime.datetime to int
 
Python Traceback
Most recent call last:
 
 File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 398, in _dispatch_request
 File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 195, in dispatch
 File "/usr/lib/python2.4/site-packages/trac/ticket/query.py", line 655, in process_request
 File "/usr/lib/python2.4/site-packages/trac/ticket/query.py", line 737, in display_html
 File "/usr/lib/python2.4/site-packages/trac/ticket/query.py", line 521, in template_data
Code fragment:
 
516. groupsequence = []
517. for ticket in tickets:
518. if orig_list:
519. # Mark tickets added or changed since the query was first
520. # executed
521. if ticket['time'] > orig_time:
522. ticket['added'] = True
523. elif ticket['changetime'] > orig_time:
524. ticket['changed'] = True
525. if self.group:
526. group_key = ticket[self.group]
 
Local variables:
Name	Value
orig_time 	datetime.datetime(2008, 3, 11, 9, 37, 33, tzinfo=<FixedOffset "UTC" ...
ticket 	{'changetime': 0, 'summary': <Element "em">, 'id': 68, 'time': 0}

[Jeroen Ruigrok van der Werven]

Does this still happen with 0.11b2?

[Christian Boos]

Duplicate of #6088, which has a patch.

[Ryan Ollos <ryano@…>]

Replying to jruigrok:

Does this still happen with 0.11b2?

I'm seeing this error with 0.11.4 when using Search.

[Christian Boos]

Replying to Ryan Ollos <ryano@…>:

I'm seeing this error with 0.11.4 when using Search.

Well, certainly not the same traceback then, as here we have an error in trac/ticket/query.py. Could you provide us with the traceback involving trac/search (and then reopen)?

[Ryan Ollos <ryano@…>]

Replying to cboos:

Well, certainly not the same traceback then, as here we have an error in trac/ticket/query.py. Could you provide us with the traceback involving trac/search (and then reopen)?

I didn't seem to get a notification for this, otherwise I would have replied earlier. Turns out my issue was due to the Doxygen plugin, and there was a patch available. See ​TH issue #3079. But yes, my error message was a bit different and I should have been more careful before reporting in this thread.