[Twisted-Python] Trial & the mock library

[Glyph]

On Jul 25, 2013, at 3:51 PM, exarkun at twistedmatrix.com wrote:

> On 08:33 pm, glyph at twistedmatrix.com wrote:
>> 
>> On Jul 25, 2013, at 8:40 AM, Jonathan Lange <jml at mumak.net> wrote:
>>> On Thu, Jul 25, 2013 at 4:14 PM, Laurens Van Houtven <_ at lvh.io> wrote:
>>> In addition to what jml said, I wonder if it makes sense for TestCase to raise when the return value of a test method is something other than None or a Deferred...
>>> 
>>> 
>>> Why stop there? Why not have a generic system to allow specifying valid return types for any function?
>> 
>> That sounds like a great idea, I wonder if anyone's thought of it before.
>> 
>> We already encode the information in epytext.  Should we make it a dependency, so it can be parsed at runtime to aid with enforcement?
> 
> Please finish the Lore -> Sphinx transition first so that we can begin investigating whether reStructuredText for API documentation is sensible.  We don't want to drag in an epytext parsing dependency if we're just going to switch to docutils in eight or nine years.

That's a good point, but I wouldn't want to block on it.  We could easily implement a simple abstraction layer for type identification that layers and translates between epydoc and ReST; we'd probably need this during the transitional period anyway, since lore->sphinx isn't pydoctor->sphinx.

Plus, of course, we'd need that abstraction layer to support multiple different styles of py3k function annotations, if we're talking about things that people might use in eight or nine years.

-glyph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20130725/d6aa6c9a/attachment-0002.html>