[TIP] testing-in-python Digest, Vol 8, Issue 3

[Noah Gift]

On 9/7/07, testing-in-python-request at lists.idyll.org
<testing-in-python-request at lists.idyll.org> wrote:
> Send testing-in-python mailing list submissions to
>         testing-in-python at lists.idyll.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.idyll.org/listinfo/testing-in-python
> or, via email, send a message with subject or body 'help' to
>         testing-in-python-request at lists.idyll.org
>
> You can reach the person managing the list at
>         testing-in-python-owner at lists.idyll.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of testing-in-python digest..."
>
>
> Today's Topics:
>
>    1. best way to deal with multi-threaded code and doctests (Noah Gift)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 7 Sep 2007 14:06:24 -0400
> From: "Noah Gift" <noah.gift at gmail.com>
> Subject: [TIP] best way to deal with multi-threaded code and doctests
> To: testing-in-python at lists.idyll.org
> Message-ID:
>         <e91cc0270709071106yc7efc7ag835c5855e9c35c5a at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> I have some code that is massively multi-threaded, but I want to make
> sure there are really good doctests as well as unittests.  It seems
> like testing a thread with a doctest is particular challenging as you
> lose control in the python interpreter.  Is there a technique to get
> around this that I am missing?

To reply to my own message, I created a "fake" get method from my
queue, but I am worried when you document something your class doesn't
do that it is a bad thing.




>
>
> Noah Gift
>
>
>
> ------------------------------
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
>
>
> End of testing-in-python Digest, Vol 8, Issue 3
> ***********************************************
>