[py-dev] capturing / doctests / py lib release

[holger krekel]

Hi py-dev, 

i am wondering if anybody would mind (or endorse) not
catching stderr by default but only stdout?  There would be a
switch ('-e' or something) that would enable capturing of
stderr as it is now.  Or should there just be a switch 
to turn off stdout/stderr capturing separately but keep 
the defaults to catch both? 

On a side note, i am probably not going to release the py lib
before end of May because of the missing fleshing out of win32
support.  Nobody, including me, has the time and will so far 
to fix things about it.  In case you haven't noticed, i am
looking for a co-developer familiar with the win32 platform(s). 
You get full commit rights and strong influence on how things 
are done on win32 and the lib in general in return, apart 
from fame and glory. 

Generalizing this: if any of you wants to help drive the py
lib please feel free to take things over.  Btw, i am very
happy that Jan Balster took over the development of a tkinter
frontend ("py.test --tkinter") which looks very promising
already. If you have suggestions or improvements for this
frontend please post to this list, Jan would be happy to get
feedback. 

I do, however, intend to work on doctest integration real soon
now.  Mind you, this is a free software programmer saying this
but then one, who also is contractually bound by the European
Union to get certain py.test related features working for PyPy
so bets are not all off.  I consider the "how to collect doctests"
issues still the primary blocker design question.

cheers, 

    holger