From holger at merlinux.eu  Wed Jul 10 15:46:54 2013
From: holger at merlinux.eu (holger krekel)
Date: Wed, 10 Jul 2013 13:46:54 +0000
Subject: [pytest-dev] next pytest bug day: August 1st
Message-ID: <20130710134654.GN27919@merlinux.eu>

Hi all,

mark your calendars!  Due to popular request i'll start doing regular 
pytest bug days, for now on the first thursday of a month.  The next one
thus is:

    Thursday, August 1st, co-ordinated through #pylib on freenode

i'll be there on my european work day and probably around
in the evening as well.  Please spread the word.

cheers,
holger

From holger at merlinux.eu  Wed Jul 10 15:56:16 2013
From: holger at merlinux.eu (holger krekel)
Date: Wed, 10 Jul 2013 13:56:16 +0000
Subject: [pytest-dev] github pytest mirror
Message-ID: <20130710135616.GP27919@merlinux.eu>

Hi again,

there now is an experimental https://github.com/hpk42/pytest mirror
which you can per-use for pull requests.  Issue tracking stays on
bitbucket.  The mirror is bidirectional but depends on me 
manual syncing for now.

Many thanks to Anatoly Bubenkoff for helping to set this up.

have forking fun,
holger


From bob.silverberg at gmail.com  Tue Jul 16 02:16:19 2013
From: bob.silverberg at gmail.com (Bob Silverberg)
Date: Mon, 15 Jul 2013 20:16:19 -0400
Subject: [pytest-dev] [pytest-rerunfailures] pytest-rerunfailures not
 using fixtures on reruns (#10)
In-Reply-To: <20130422082733.GQ5855@merlinux.eu>
References: <klrmn/pytest-rerunfailures/issues/10@github.com>
	<klrmn/pytest-rerunfailures/issues/10/16363644@github.com>
	<CAA9LNDeUfsN7N0ivswJ1an4t-jb=7xuDCiBvHOr7bMDGW_N0KA@mail.gmail.com>
	<20130422082733.GQ5855@merlinux.eu>
Message-ID: <CAOwbyXeAwbYOQVurfKg-QAsA8P2ppB=9hj7PubWA1GM81pGo2w@mail.gmail.com>

Hi Holger,

Sorry to take so ridiculously long to respond to this. I have tried my
reduced test case with pytest 2.3.5 and the problem does seem to be fixed.

Thanks for your help,
Bob



On Mon, Apr 22, 2013 at 4:27 AM, holger krekel <holger at merlinux.eu> wrote:

> Hi Leah, Bob,
>
> On Fri, Apr 19, 2013 at 20:55 -0700, Leah Klearman wrote:
> > Hi Holger and other py.test mavens,
> >
> > Bob has reported a problem with my py.test plugin pytest-rerunfailures
> [1]
> > not re-running the setup before rerunning the test.
> >
> > Looking at my code, it has pytest_runtest_protocol() [2] looping
> > on _pytest.runner.runtestprotocol() [3], which in turn runs the setup,
> the
> > test, and the teardown.
> >
> > [1] https://github.com/klrmn/pytest-rerunfailures
> > [2]
> >
> https://github.com/klrmn/pytest-rerunfailures/blob/master/rerunfailures/plugin.py#L46
> > [3]
> >
> https://bitbucket.org/hpk42/pytest/src/fdc28ac2029f1c0be1dac4991c2f1b014c39a03f/_pytest/runner.py?at=default#cl-65
> >
> > I haven't taken the hours needed to get my head fully into py.test plugin
> > development mode, but I'm not sure I can implement a fix at my layer.
> >
> >
> > I'm hoping someone here will have some insight.
>
> It's a bit intricate.  A function item keeps around some fixture state
> and was so far not intended to be run multiple times.  I went ahead and
> tried to improve the behaviour to better allow re-running.   Please try
> with
>
>     pip install -i http://pypi.testrun.org -U pytest
>
> which should give you pytest-2.3.5.dev16 at least.  This is bound to be
> released soon so quick feedback is welcome.  If you still have problems
> please try to send a minimal test file which shows undesired behaviour.
>
> A word of warning: your calling of runtestprotocol() is not quite right
> and might lead to problems.  "nextitem" should really be the item that
> is going to be run next.  So if you re-run three times the first two
> invocations should have nextitem=item.
>
> best,
> holger
>
>
> > Thanks,
> > -Leah
> >
> >
> > On Sun, Apr 14, 2013 at 6:29 PM, Bob Silverberg <
> notifications at github.com>wrote:
> >
> > > I just verified this behaviour myself with a simple test [1]. I see it
> > > with both funcargs and fixtures, but I'm not sure if it has to do with
> the
> > > plugin, or the way py.test works. It does inject the value into the
> test
> > > method, but it doesn't rerun the fixture, so it seems like it is
> caching
> > > the first run of the fixture and using that on subsequent runs.
> > >
> > > I'm not sure if this is something that the plugin can have any effect
> on,
> > > or if it's just the way fixtures work. It is specified for this fixture
> > > that it is scope='function', and perhaps py.test makes that happen by
> > > checking the function name, which is, of course, the same for each
> run. I
> > > did try removing the scope argument from the fixture but that had no
> > > effect.
> > >
> > > Do you have any thoughts about this, @klrmn <https://github.com/klrmn
> >?
> > >
> > > [1] https://gist.github.com/bobsilverberg/5385035
> > >
> > > ?
> > > Reply to this email directly or view it on GitHub<
> https://github.com/klrmn/pytest-rerunfailures/issues/10#issuecomment-16363644
> >
> > > .
> > >
>
> > _______________________________________________
> > Pytest-dev mailing list
> > Pytest-dev at python.org
> > http://mail.python.org/mailman/listinfo/pytest-dev
>
>


-- 
Bob Silverberg
www.silverwareconsulting.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20130715/3e34b50a/attachment.html>

From holger at merlinux.eu  Tue Jul 16 11:36:37 2013
From: holger at merlinux.eu (holger krekel)
Date: Tue, 16 Jul 2013 09:36:37 +0000
Subject: [pytest-dev] new "professional testing with Python" training in
	germany
Message-ID: <20130716093637.GM3125@merlinux.eu>


For those interested, i am giving another open "professional testing
with Python" training at the PythonAcademy in Leipzig, end November.
For details:

http://www.python-academy.com/courses/specialtopics/python_course_testing.html

feel free to mail me personally if you have any questions.

cheers,
holger

From holger at merlinux.eu  Tue Jul 23 09:34:15 2013
From: holger at merlinux.eu (holger krekel)
Date: Tue, 23 Jul 2013 07:34:15 +0000
Subject: [pytest-dev] first pytest bug day 1st August 2013
Message-ID: <20130723073415.GC7975@merlinux.eu>

Hi pytesters,

First of August is going to see the first public pytest-bug-thursday.
We'll co-ordinate through #pylib on irc.freenode.net, and i'll be
present at german office times as well as in the evening.  Hope to see
many of you helping to fix bugs and prepare the pytest-2.4 release!
There is something for everybody to trickle, we have a full bucket :)

cheers,
holger

From holger at merlinux.eu  Wed Jul 31 09:21:11 2013
From: holger at merlinux.eu (holger krekel)
Date: Wed, 31 Jul 2013 07:21:11 +0000
Subject: [pytest-dev] pytest bug day tomorrow
Message-ID: <20130731072111.GC3987@merlinux.eu>

Hi again,

just a quick reminder that tomorrow is pytest bug day, torwards
the 2.4 release!  See you on #pylib. 

cheers,
holger