Modify ↓
#7705 closed defect (fixed)
unit test failure with pygments 0.11.1dev
| Reported by: | Christian Boos | Owned by: | Tim Hatch |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11.2 |
| Component: | rendering | Version: | 0.11-stable |
| Severity: | normal | Keywords: | pygments |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Using pygments:56c3e7e93e27 (latest tip in pygments-main as of today), I get the following failure in Trac's unit tests:
FAIL: test_newline_content (trac.mimeview.tests.pygments.PygmentsRendererTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Workspace\src\trac\repos\trunk\trac\mimeview\tests\pygments.py", line 103, in test_newline_content
self.assertEqual("\n\n\n", t)
AssertionError: '\n\n\n' != u'\n\n\n\n'
Looking at the code, it seems that u'\n\n\n\n' should actually be the more correct result and that '\n\n\n' was the sub-optimal result we had up to now.
Tim, could you please look at this and eventually add a kind of version check to the test?
Attachments (0)
Note:
See TracTickets
for help on using tickets.



I haven't checked yet, but this is most likely caused by http://dev.pocoo.org/projects/pygments/changeset/a471fde4e814
I'll update later today.