No, it crashes with an AttributeError:

```
    @unittest.expectedFailure
AttributeError: 'module' object has no attribute 'expectedFailure'
```

2.6's unittest is really quite limited to that of 2.7. We could work around it, but it would require:
backporting/implementing `unittest.expectedFailure` and a few `unittest.TestCase` methods `assertIs`, `assertRegexpMatches`, etc and working around missing `unittest.skipUnless`.