[TIP] Green and Red bars
markroddy at gmail.com
Thu Oct 21 13:44:05 PDT 2010
On Thu, Oct 21, 2010 at 4:00 PM, Michael Foord
<fuzzyman at voidspace.org.uk> wrote:
> On 21 Oct 2010, at 20:37, Mark Roddy <markroddy at gmail.com> wrote:
>> On Thu, Oct 21, 2010 at 2:12 PM, Éric Araujo <merwok at netwok.org> wrote:
>>> Le 21/10/2010 17:03, Michael Foord a écrit :
>>>> On 21/10/2010 16:01, Olemis Lang wrote:
>>>>> Is it a good idea to add a similar Tkinter GUI runner in stdlib (even
>>>>> if it is outside unittest module , let's say e.g. in unittestgui
>>>>> module) ?
>>>> It could live in tools and I certainly wouldn't be opposed to it. It is
>>>> something I have considered, especially now that unittest does test
>>>> discovery, I just haven't had time to work on it.
>>> Olemis, can you open a feature request against 3.2 on bugs.python.org?
>>> Thanks in advance.
>>> testing-in-python mailing list
>>> testing-in-python at lists.idyll.org
>> I should note that I only checked the GUI against python 2.6. I
>> imagine it will probably require more changes to support 3.2. I can
>> check this later (I don't have a 3.x install on my work machine).
> Ah, porting to Python 3 is easy. :-)
> Not that it wouldn't be good if you did it. Double bonus points for using ttk.
>> testing-in-python mailing list
>> testing-in-python at lists.idyll.org
If anyone's interested, I did a small proof of concept on converting
the gui to use test discovery instead of a user specified callable and
posted it to bitbucket. I'll look into how bad the Python 3
conversion would be, though I think it might make more sense to iron
out what changes need to be made to better support discover before
doing a fork to support 3.x (if necessary).
More information about the testing-in-python