Error while browsing (updating) a SVN repository

[Emmanuel Blot]

Trac Version

Using [2979]

How it happened

After a new commit to Subversion, browse the timeline, select the last changeset event: (http://<server>/trac/<project>/changeset/55).

Notes:

• Previous changesets can be browsed without any issue.
• Previous changesets have been commited and browsed with the same Trac version & environment (Trac engine has been updated between changeset [39] and [40], first error occured with changeset [55])

Python Traceback

Traceback (most recent call last):
  File "/local/engine/trac/trac/web/main.py", line 283, in dispatch_request
    dispatcher.dispatch(req)
  File "/local/engine/trac/trac/web/main.py", line 170, in dispatch
    resp = chosen_handler.process_request(req)
  File "/local/engine/trac/trac/versioncontrol/web_ui/changeset.py", line 216, in process_request
    diff_args, diff_options)
  File "/local/engine/trac/trac/versioncontrol/web_ui/changeset.py", line 441, in _render_html
    props = _prop_changes(old_node, new_node)
  File "/local/engine/trac/trac/versioncontrol/web_ui/changeset.py", line 374, in _prop_changes
    props.update(name=name)
TypeError: update() takes no keyword arguments

[Christian Boos]

Yeah, sorry about that, I tend to use Python 2.4 quite exclusively those days. Mark Rowe fixed that already in r3013.

[Emmanuel Blot]

Ok, no pb.

The trouble is that Python 2.4 is not available on every platform (not on Linux/Debian, for example: several dependencies are missing).

I think we should introduce a supplementary test to validate the Python syntax - against a particular version, shouldn't we ?

[Matthew Good]

Well, I don't understand why the line wasn't just

props['name'] = name

But, eblot yes you can run the unit tests with Python 2.3 to try to catch an incompatibilities.