<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Feb 6, 2012, at 10:48 AM, Jonathan Lange wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">In my ideal world, Twisted's TestCase would inherit from testtools's<br>TestCase and would continue to provide the same API it does today.<br>This might not be everyone else's ideal though, and the path from here<br>to there is unclear to me. I welcome your thoughts.<br></span></span></blockquote></div><br><div>Users still routinely struggle with the one dependency we allowed Twisted core to have - zope.interface. I do still think that's worth it, since it freed us from a significant and complex maintenance burden. And I do sometimes wish that we could make it an optional or bundled dependency, to give users who have to download Twisted themselves a gentler on-ramp. By your own admission, however, the person who should be doing maintenance on trial and the person doing maintenance on testtools are mostly the same guy :-).</div><div><br></div><div>While testtools' features are nice, and I will likely even elect to use myself it for testing some Twisted applications in the future, I would set the bar <i>very</i> high for making testtools a required dependency for Twisted's own test suite. Just for starters, the Python packaging ecosystem disaster would need to be fixed; also, the name of the package should be changed to be more unique so that users wouldn't find things like <<a href="http://www.testtools.com/">http://www.testtools.com/</a>> and <<a href="https://github.com/ferruhy/testtools">https://github.com/ferruhy/testtools</a>> when searching around the web for the contents of the inevitable packaging error message.</div><div><br></div><div>-glyph</div><div><br></div></body></html>