#9684 closed defect (duplicate)
cannot view changeset after svn commit / recursion limit reached — at Version 2
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.10.4 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
I commited my local changes and went to see the changeset. But had a problem viewing it. The error says (in the title of page): "maximum recursion depth exceeded in cmp"
We tested if the changes were really commited to the repo and saw that they were. We can update our local copy, but cannt view the changeset via trac. The traceback is:
Python Traceback (long ugly trace back…)
...
while besti+bestsize < ahi and bestj+bestsize < bhi and \
RuntimeError: maximum recursion depth exceeded in cmp
Change History (2)
comment:1 by , 14 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
comment:2 by , 14 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.
Well, googling for "maximum recursion depth exceeded in cmp" would have given you the duplicate: #3483.
Upgrade to a newer version of Python (2.4.3 should do).