On Thu, 2011-04-28 at 19:59 +0200, Baptiste Lepilleur wrote: > Upgrading to 2.0.3 has indeed fixed the issue (the empty traceback no > longer appear). > > > Though I don't really see an issue corresponding to that in the > changelog...
[snip]
Changes between 2.0.0 and 2.0.1
----------------------------------------------
- refine and unify initial capturing so that it works nicely
even if the logging module is used on an early-loaded conftest.py
file or plugin.
[snip]
it's not obvious unless you know what it means.
-- Ronny
> Thanks,
> Baptiste.
>
> 2011/4/28 Ronny Pfannschmidt <ronny.pfannschm...@gmx.de>
>
> On Thu, 2011-04-28 at 09:54 +0200, Baptiste Lepilleur wrote:
> >
> >
> > 2011/4/28 Ronny Pfannschmidt <ronny.pfannschm...@gmx.de>
> >
> > On Wed, 2011-04-27 at 22:29 +0200, Baptiste
> Lepilleur wrote:
> > > Hi,
> > [...]
> > >
> > > Notes that the traceback is empty. Any idea of
> what could
> > explain
> > > that?
> >
> >
> > can you retry with a more recent py.test
> > afair this problem has been fixed after 1.3.4
> >
> > also i would suggest to follow the py.test
> convention and name
> > the test
> > files test_{foo} instead {foo}test
> >
> >
> >
> > What is the procedure for upgrading an existing install done
> > easy_install? Do I just reinstall using the latest tarball?
> Or do I
> > need to remove previous module manually (If so is it just
> py.test
> > module)?
> >
>
> easy_install -U pytest
> since easy_install wont upgrade already installed packages
> unless asked
> to
>
> -- Ronny
>
> >
> > Thanks,
> > Baptiste.
> >
> >
> >
>
>
>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
