From bubenkoff at gmail.com  Sun Mar  1 12:02:04 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Sun, 1 Mar 2015 12:02:04 +0100
Subject: [pytest-dev] commit messages from drone
In-Reply-To: <20150228205402.GT17945@merlinux.eu>
References: <20150228205020.19154.16752@drone.io>
 <20150228205402.GT17945@merlinux.eu>
Message-ID: <CACTnz+E9n2hBN0n0X7wQYFPBA7PQasTem6Hgc8ce3XcU0ahDDA@mail.gmail.com>

changed it to send only the failures

On 28 February 2015 at 21:54, holger krekel <holger at merlinux.eu> wrote:

> Is there a configuration where only failures are sent
> to the list?  It's a bit verbose as it stands IMHO.
> And maybe just the author in the commit should get
> success mails for a commit.
>
> holger
>
> On Sat, Feb 28, 2015 at 20:50 +0000, Drone.io Build wrote:
> > Build was Successful
> >
> > Build      : https://drone.io/bitbucket.org/pytest-dev/pytest/13
> > Project    : https://drone.io/bitbucket.org/pytest-dev/pytest
> >
> > Repository : https://bitbucket.org/pytest-dev/pytest
> > Version    : 3892:ebe73a63994f
> > Author     : Anatoly Bubenkov <bubenkoff at gmail.com>
> > Branch     : plugincompat-move
> >
> > Message:
> > Close branch plugincompat-move
> >
>
> > _______________________________________________
> > pytest-commit mailing list
> > pytest-commit at python.org
> > https://mail.python.org/mailman/listinfo/pytest-commit
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150301/ae771493/attachment.html>

From tom at viner.tv  Mon Mar  2 00:01:12 2015
From: tom at viner.tv (Tom Viner)
Date: Sun, 1 Mar 2015 23:01:12 +0000
Subject: [pytest-dev] Enabling viewing of rewritten AST trees as Python
In-Reply-To: <CAAWk_DwXL-e=a_moHECQV77end9nSHnzEeSZukwzezWcS=cc=w@mail.gmail.com>
References: <CANBSuyGTKNfvv8SNoqf4orfi_d_OGpdaDoQ3oy1V7y=4a7pYng@mail.gmail.com>
 <CAAWk_DwXL-e=a_moHECQV77end9nSHnzEeSZukwzezWcS=cc=w@mail.gmail.com>
Message-ID: <CANBSuyHxvURzTP+1zhxUG5DgDVO-jbO_grokwkq3XQqKt6DEbQ@mail.gmail.com>

Thanks for your ideas Floris, I've managed to get it working with
your pytest_configure suggestion.

The only extra bit was having to disable reading the cached pyc files that
pytest writes, as these skip my monkeypatch.

Take a look, it's simple to use:
https://gist.github.com/tomviner/c3537c2f2b2b8172f83e

If there's any demand, I could easily make this a pip installable pytest
plugin.

On 13 November 2014 at 23:34, Floris Bruynooghe <flub at devork.be> wrote:

> Hi Tom,
>
> On 9 November 2014 19:18, Tom Viner <tom at viner.tv> wrote:
> > The four options I can think of to gain access to this variable:
> > - monkey patch rewrite.rewrite_asserts
> > - edit rewrite_asserts and paste in the logging code above:
> >     -- temporarily, by each developer, on each occasion required
> >     -- permanently, but only running when a certain debug flag is active
> > - expose the rewritten AST via a new hook
> >
> > monkey patch is my preferred option, because if I can make it work, a
> plugin
> > could be written. I just need some help to find an appropriate hook to do
> > the monkey patching before pytest gets going with the
> AssertionRewritingHook
> > and calls rewrite_asserts. Without knowledge of an early-running hook, I
> > could only get this working by patching rewrite_asserts then calling
> > pytest.main myself, see
> > https://gist.github.com/tomviner/13c95cdb1e159028fc0b
>
> Would this work by using monkeypatching, but using a method on
> _pytest.pytester.TmpTestDir which wraps around inline_run or
> inline_runsource?  That would seem like a fairly reasonable approach.
> It could simply skip with an appropriate message if the meta lib is
> importable and print the reversed python code to stdout for capsys to
> collect.
>
> If you would like to go the full plugin way I believe you just need to
> hook in before collection happens.  I imagine pytest_configure would
> be a reasonable hook for that, but have to admit I haven't tried it.
>
>
> Regards,
> Floris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150301/febf6478/attachment.html>

From bubenkoff at gmail.com  Mon Mar  2 08:10:59 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Mon, 2 Mar 2015 08:10:59 +0100
Subject: [pytest-dev] commit messages from drone
In-Reply-To: <20150228205402.GT17945@merlinux.eu>
References: <20150228205020.19154.16752@drone.io>
 <20150228205402.GT17945@merlinux.eu>
Message-ID: <CACTnz+EERa7BchGtDxytOZ2iBCJ4QfUEip95BBAaz9DAvrMN5w@mail.gmail.com>

Yes it can report only failures
I'll change
On Feb 28, 2015 9:54 PM, "holger krekel" <holger at merlinux.eu> wrote:

> Is there a configuration where only failures are sent
> to the list?  It's a bit verbose as it stands IMHO.
> And maybe just the author in the commit should get
> success mails for a commit.
>
> holger
>
> On Sat, Feb 28, 2015 at 20:50 +0000, Drone.io Build wrote:
> > Build was Successful
> >
> > Build      : https://drone.io/bitbucket.org/pytest-dev/pytest/13
> > Project    : https://drone.io/bitbucket.org/pytest-dev/pytest
> >
> > Repository : https://bitbucket.org/pytest-dev/pytest
> > Version    : 3892:ebe73a63994f
> > Author     : Anatoly Bubenkov <bubenkoff at gmail.com>
> > Branch     : plugincompat-move
> >
> > Message:
> > Close branch plugincompat-move
> >
>
> > _______________________________________________
> > pytest-commit mailing list
> > pytest-commit at python.org
> > https://mail.python.org/mailman/listinfo/pytest-commit
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150302/991697c9/attachment.html>

From tom at viner.tv  Mon Mar  2 10:06:08 2015
From: tom at viner.tv (Tom Viner)
Date: Mon, 2 Mar 2015 09:06:08 +0000
Subject: [pytest-dev] Enabling viewing of rewritten AST trees as Python
In-Reply-To: <CANBSuyHxvURzTP+1zhxUG5DgDVO-jbO_grokwkq3XQqKt6DEbQ@mail.gmail.com>
References: <CANBSuyGTKNfvv8SNoqf4orfi_d_OGpdaDoQ3oy1V7y=4a7pYng@mail.gmail.com>
 <CAAWk_DwXL-e=a_moHECQV77end9nSHnzEeSZukwzezWcS=cc=w@mail.gmail.com>
 <CANBSuyHxvURzTP+1zhxUG5DgDVO-jbO_grokwkq3XQqKt6DEbQ@mail.gmail.com>
Message-ID: <CANBSuyG=qo-uJ8rvG3uh9Yk3X-EwUXuxdwgb6MqronewggGg-Q@mail.gmail.com>

One extra note:

`py.test -s` is required to see rewritten AST output, even for failing
tests, because the output comes while
tests are being collected and rewritten, not during the execution of a
test. So pytest's "show output upon
fail" cannot help here.

If anyone knows how to tie the output to particular tests, that would be
great.


On 1 March 2015 at 23:01, Tom Viner <tom at viner.tv> wrote:

> Thanks for your ideas Floris, I've managed to get it working with
> your pytest_configure suggestion.
>
> The only extra bit was having to disable reading the cached pyc files that
> pytest writes, as these skip my monkeypatch.
>
> Take a look, it's simple to use:
> https://gist.github.com/tomviner/c3537c2f2b2b8172f83e
>
> If there's any demand, I could easily make this a pip installable pytest
> plugin.
>
> On 13 November 2014 at 23:34, Floris Bruynooghe <flub at devork.be> wrote:
>
>> Hi Tom,
>>
>> On 9 November 2014 19:18, Tom Viner <tom at viner.tv> wrote:
>> > The four options I can think of to gain access to this variable:
>> > - monkey patch rewrite.rewrite_asserts
>> > - edit rewrite_asserts and paste in the logging code above:
>> >     -- temporarily, by each developer, on each occasion required
>> >     -- permanently, but only running when a certain debug flag is active
>> > - expose the rewritten AST via a new hook
>> >
>> > monkey patch is my preferred option, because if I can make it work, a
>> plugin
>> > could be written. I just need some help to find an appropriate hook to
>> do
>> > the monkey patching before pytest gets going with the
>> AssertionRewritingHook
>> > and calls rewrite_asserts. Without knowledge of an early-running hook, I
>> > could only get this working by patching rewrite_asserts then calling
>> > pytest.main myself, see
>> > https://gist.github.com/tomviner/13c95cdb1e159028fc0b
>>
>> Would this work by using monkeypatching, but using a method on
>> _pytest.pytester.TmpTestDir which wraps around inline_run or
>> inline_runsource?  That would seem like a fairly reasonable approach.
>> It could simply skip with an appropriate message if the meta lib is
>> importable and print the reversed python code to stdout for capsys to
>> collect.
>>
>> If you would like to go the full plugin way I believe you just need to
>> hook in before collection happens.  I imagine pytest_configure would
>> be a reasonable hook for that, but have to admit I haven't tried it.
>>
>>
>> Regards,
>> Floris
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150302/04afac32/attachment-0001.html>

From nicoddemus at gmail.com  Tue Mar  3 00:52:53 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 2 Mar 2015 20:52:53 -0300
Subject: [pytest-dev] pytest-faulthandler
Message-ID: <CA+RQFffz0NAS=AhVXq32c96RbZagK9Nb-LPZVhXyjCg4nkDSpQ@mail.gmail.com>

Hi all,

Just released version 0.1 of the pytest-faulthandler plugin:

PyPI: https://pypi.python.org/pypi/pytest-faulthandler
GitHub: https://github.com/nicoddemus/pytest-faulthandler

This plugin enables the fault handler module when running tests using
py.test, inspired by nose-faulthandler.

Feedback is welcome!

Cheers,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150302/2f02dc8d/attachment.html>

From bubenkoff at gmail.com  Tue Mar  3 08:46:10 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Tue, 3 Mar 2015 08:46:10 +0100
Subject: [pytest-dev] pytest-faulthandler
In-Reply-To: <CA+RQFffz0NAS=AhVXq32c96RbZagK9Nb-LPZVhXyjCg4nkDSpQ@mail.gmail.com>
References: <CA+RQFffz0NAS=AhVXq32c96RbZagK9Nb-LPZVhXyjCg4nkDSpQ@mail.gmail.com>
Message-ID: <CACTnz+FCRgf_WmNSsFROkt4o01+1oF1FfEdxcXZuLgcXEvaGDw@mail.gmail.com>

nice project!
I guess that's for testing python c extensions, mostly?
BTW: not under pytest-dev? :)

On 3 March 2015 at 00:52, Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi all,
>
> Just released version 0.1 of the pytest-faulthandler plugin:
>
> PyPI: https://pypi.python.org/pypi/pytest-faulthandler
> GitHub: https://github.com/nicoddemus/pytest-faulthandler
>
> This plugin enables the fault handler module when running tests using
> py.test, inspired by nose-faulthandler.
>
> Feedback is welcome!
>
> Cheers,
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>


-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150303/0e226e23/attachment.html>

From bubenkoff at gmail.com  Tue Mar  3 08:57:12 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Tue, 3 Mar 2015 08:57:12 +0100
Subject: [pytest-dev] moving repos under pytest-dev on bitbucket
Message-ID: <CACTnz+FLVXbWMu0vhhGKfr+rFo4L2fm0TQ=3166iync=ckMWnw@mail.gmail.com>

I notices interesting issue with moving repositories under pytest-dev
When some user sends the transfer request and SOMEONE ELSE approves it, bb
set's the APPROVING person as a creator, so original creator looses his
admin rights.
I think we should not approve requests ourself instead the user should
approve his request himself - this way he'll keep admin rights properly.
But this requires adding the user to the pytest-dev team BEFORE sending the
request.

-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150303/478ae6ae/attachment.html>

From nicoddemus at gmail.com  Tue Mar  3 11:41:59 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 3 Mar 2015 07:41:59 -0300
Subject: [pytest-dev] pytest-faulthandler
In-Reply-To: <CACTnz+FCRgf_WmNSsFROkt4o01+1oF1FfEdxcXZuLgcXEvaGDw@mail.gmail.com>
References: <CA+RQFffz0NAS=AhVXq32c96RbZagK9Nb-LPZVhXyjCg4nkDSpQ@mail.gmail.com>
 <CACTnz+FCRgf_WmNSsFROkt4o01+1oF1FfEdxcXZuLgcXEvaGDw@mail.gmail.com>
Message-ID: <CA+RQFffH4OVRXU-Uq7UONg2MTO7PoFSc2hNNy8ncq+QJYuuJHg@mail.gmail.com>

Thanks Anatoly! :)

Yes, this is mostly for projects that have C extensions.

I did not move this under pytest-dev immediately because I thought I would
like first to see if others' feedback first. You think I should move it
right now?

Chhers,

On Tue, Mar 3, 2015 at 4:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
wrote:

> nice project!
> I guess that's for testing python c extensions, mostly?
> BTW: not under pytest-dev? :)
>
> On 3 March 2015 at 00:52, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>
>> Hi all,
>>
>> Just released version 0.1 of the pytest-faulthandler plugin:
>>
>> PyPI: https://pypi.python.org/pypi/pytest-faulthandler
>> GitHub: https://github.com/nicoddemus/pytest-faulthandler
>>
>> This plugin enables the fault handler module when running tests using
>> py.test, inspired by nose-faulthandler.
>>
>> Feedback is welcome!
>>
>> Cheers,
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>
>
> --
> Anatoly Bubenkov
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150303/24fed968/attachment.html>

From bubenkoff at gmail.com  Tue Mar  3 11:44:56 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Tue, 3 Mar 2015 11:44:56 +0100
Subject: [pytest-dev] pytest-faulthandler
In-Reply-To: <CA+RQFffH4OVRXU-Uq7UONg2MTO7PoFSc2hNNy8ncq+QJYuuJHg@mail.gmail.com>
References: <CA+RQFffz0NAS=AhVXq32c96RbZagK9Nb-LPZVhXyjCg4nkDSpQ@mail.gmail.com>
 <CACTnz+FCRgf_WmNSsFROkt4o01+1oF1FfEdxcXZuLgcXEvaGDw@mail.gmail.com>
 <CA+RQFffH4OVRXU-Uq7UONg2MTO7PoFSc2hNNy8ncq+QJYuuJHg@mail.gmail.com>
Message-ID: <CACTnz+GTkTDN6AcsGAboE7axfbcNwcuVxT1rcgHxwAT34QD8Dw@mail.gmail.com>

well, in my opinion, this check-through-mailing-list should only be applied
for the persons who are not yet in the team
@team, any objections on this approach?
i've created 2 plugins under pytest-dev recently without explicit approval,
so then i was wrong probably

On 3 March 2015 at 11:41, Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Thanks Anatoly! :)
>
> Yes, this is mostly for projects that have C extensions.
>
> I did not move this under pytest-dev immediately because I thought I would
> like first to see if others' feedback first. You think I should move it
> right now?
>
> Chhers,
>
> On Tue, Mar 3, 2015 at 4:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
> wrote:
>
>> nice project!
>> I guess that's for testing python c extensions, mostly?
>> BTW: not under pytest-dev? :)
>>
>> On 3 March 2015 at 00:52, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Just released version 0.1 of the pytest-faulthandler plugin:
>>>
>>> PyPI: https://pypi.python.org/pypi/pytest-faulthandler
>>> GitHub: https://github.com/nicoddemus/pytest-faulthandler
>>>
>>> This plugin enables the fault handler module when running tests using
>>> py.test, inspired by nose-faulthandler.
>>>
>>> Feedback is welcome!
>>>
>>> Cheers,
>>>
>>> _______________________________________________
>>> pytest-dev mailing list
>>> pytest-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>
>>>
>>
>>
>> --
>> Anatoly Bubenkov
>>
>
>


-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150303/5fe69ea6/attachment-0001.html>

From holger at merlinux.eu  Tue Mar  3 16:07:31 2015
From: holger at merlinux.eu (holger krekel)
Date: Tue, 3 Mar 2015 15:07:31 +0000
Subject: [pytest-dev] pytest-faulthandler
In-Reply-To: <CACTnz+GTkTDN6AcsGAboE7axfbcNwcuVxT1rcgHxwAT34QD8Dw@mail.gmail.com>
References: <CA+RQFffz0NAS=AhVXq32c96RbZagK9Nb-LPZVhXyjCg4nkDSpQ@mail.gmail.com>
 <CACTnz+FCRgf_WmNSsFROkt4o01+1oF1FfEdxcXZuLgcXEvaGDw@mail.gmail.com>
 <CA+RQFffH4OVRXU-Uq7UONg2MTO7PoFSc2hNNy8ncq+QJYuuJHg@mail.gmail.com>
 <CACTnz+GTkTDN6AcsGAboE7axfbcNwcuVxT1rcgHxwAT34QD8Dw@mail.gmail.com>
Message-ID: <20150303150731.GB17945@merlinux.eu>

On Tue, Mar 03, 2015 at 11:44 +0100, Anatoly Bubenkov wrote:
> well, in my opinion, this check-through-mailing-list should only be applied
> for the persons who are not yet in the team
> @team, any objections on this approach?
> i've created 2 plugins under pytest-dev recently without explicit approval,
> so then i was wrong probably

I think it's good to have every plugin go through the mailing list
and be approved and merged by one other person than the one suggesting it.
It's also a way of noticing what is hosted within pytest-dev and
avoiding duplicate efforts.

holger

> On 3 March 2015 at 11:41, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> > Thanks Anatoly! :)
> >
> > Yes, this is mostly for projects that have C extensions.
> >
> > I did not move this under pytest-dev immediately because I thought I would
> > like first to see if others' feedback first. You think I should move it
> > right now?
> >
> > Chhers,
> >
> > On Tue, Mar 3, 2015 at 4:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
> > wrote:
> >
> >> nice project!
> >> I guess that's for testing python c extensions, mostly?
> >> BTW: not under pytest-dev? :)
> >>
> >> On 3 March 2015 at 00:52, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> >>
> >>> Hi all,
> >>>
> >>> Just released version 0.1 of the pytest-faulthandler plugin:
> >>>
> >>> PyPI: https://pypi.python.org/pypi/pytest-faulthandler
> >>> GitHub: https://github.com/nicoddemus/pytest-faulthandler
> >>>
> >>> This plugin enables the fault handler module when running tests using
> >>> py.test, inspired by nose-faulthandler.
> >>>
> >>> Feedback is welcome!
> >>>
> >>> Cheers,
> >>>
> >>> _______________________________________________
> >>> pytest-dev mailing list
> >>> pytest-dev at python.org
> >>> https://mail.python.org/mailman/listinfo/pytest-dev
> >>>
> >>>
> >>
> >>
> >> --
> >> Anatoly Bubenkov
> >>
> >
> >
> 
> 
> -- 
> Anatoly Bubenkov

> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From ralf at systemexit.de  Tue Mar  3 23:19:28 2015
From: ralf at systemexit.de (Ralf Schmitt)
Date: Tue, 03 Mar 2015 23:19:28 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
Message-ID: <87k2yxrafj.fsf@hummelbi.lan>

Hi,

pytest-twisted is a plugin for pytest, which allows to test code, which
uses the twisted framework.

pytest-twisted needs a new maintainer. The code is on github [1], so I
think it would make sense to move it to the new pytest-dev organization.

Is anyone interested in maintaining it and moving it over to the
pytest-dev organization?

[1] https://github.com/schmir/pytest-twisted

-- 
Cheers
Ralf

From bubenkoff at gmail.com  Wed Mar  4 09:20:44 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Wed, 4 Mar 2015 09:20:44 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <87k2yxrafj.fsf@hummelbi.lan>
References: <87k2yxrafj.fsf@hummelbi.lan>
Message-ID: <CACTnz+FqoT43t81M5GiNjRFTycinJhr_TGUqSKgoWCG=YLdptA@mail.gmail.com>

i suggest moving under pytest-dev as a first step (and add pypi access to
at least 2 team members), without having an explicit maintainer

On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:

> Hi,
>
> pytest-twisted is a plugin for pytest, which allows to test code, which
> uses the twisted framework.
>
> pytest-twisted needs a new maintainer. The code is on github [1], so I
> think it would make sense to move it to the new pytest-dev organization.
>
> Is anyone interested in maintaining it and moving it over to the
> pytest-dev organization?
>
> [1] https://github.com/schmir/pytest-twisted
>
> --
> Cheers
> Ralf
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150304/c49063de/attachment.html>

From bubenkoff at gmail.com  Wed Mar  4 09:39:41 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Wed, 4 Mar 2015 09:39:41 +0100
Subject: [pytest-dev] pytest-faulthandler
In-Reply-To: <20150303150731.GB17945@merlinux.eu>
References: <CA+RQFffz0NAS=AhVXq32c96RbZagK9Nb-LPZVhXyjCg4nkDSpQ@mail.gmail.com>
 <CACTnz+FCRgf_WmNSsFROkt4o01+1oF1FfEdxcXZuLgcXEvaGDw@mail.gmail.com>
 <CA+RQFffH4OVRXU-Uq7UONg2MTO7PoFSc2hNNy8ncq+QJYuuJHg@mail.gmail.com>
 <CACTnz+GTkTDN6AcsGAboE7axfbcNwcuVxT1rcgHxwAT34QD8Dw@mail.gmail.com>
 <20150303150731.GB17945@merlinux.eu>
Message-ID: <CACTnz+EVGgjLB3RvYSCf+ZJW15eiHj_Caj9ni2DWAvUfQqAzWw@mail.gmail.com>

ok, agree

On 3 March 2015 at 16:07, holger krekel <holger at merlinux.eu> wrote:

> On Tue, Mar 03, 2015 at 11:44 +0100, Anatoly Bubenkov wrote:
> > well, in my opinion, this check-through-mailing-list should only be
> applied
> > for the persons who are not yet in the team
> > @team, any objections on this approach?
> > i've created 2 plugins under pytest-dev recently without explicit
> approval,
> > so then i was wrong probably
>
> I think it's good to have every plugin go through the mailing list
> and be approved and merged by one other person than the one suggesting it.
> It's also a way of noticing what is hosted within pytest-dev and
> avoiding duplicate efforts.
>
> holger
>
> > On 3 March 2015 at 11:41, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> >
> > > Thanks Anatoly! :)
> > >
> > > Yes, this is mostly for projects that have C extensions.
> > >
> > > I did not move this under pytest-dev immediately because I thought I
> would
> > > like first to see if others' feedback first. You think I should move it
> > > right now?
> > >
> > > Chhers,
> > >
> > > On Tue, Mar 3, 2015 at 4:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
> > > wrote:
> > >
> > >> nice project!
> > >> I guess that's for testing python c extensions, mostly?
> > >> BTW: not under pytest-dev? :)
> > >>
> > >> On 3 March 2015 at 00:52, Bruno Oliveira <nicoddemus at gmail.com>
> wrote:
> > >>
> > >>> Hi all,
> > >>>
> > >>> Just released version 0.1 of the pytest-faulthandler plugin:
> > >>>
> > >>> PyPI: https://pypi.python.org/pypi/pytest-faulthandler
> > >>> GitHub: https://github.com/nicoddemus/pytest-faulthandler
> > >>>
> > >>> This plugin enables the fault handler module when running tests using
> > >>> py.test, inspired by nose-faulthandler.
> > >>>
> > >>> Feedback is welcome!
> > >>>
> > >>> Cheers,
> > >>>
> > >>> _______________________________________________
> > >>> pytest-dev mailing list
> > >>> pytest-dev at python.org
> > >>> https://mail.python.org/mailman/listinfo/pytest-dev
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Anatoly Bubenkov
> > >>
> > >
> > >
> >
> >
> > --
> > Anatoly Bubenkov
>
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150304/4610354f/attachment.html>

From holger at merlinux.eu  Thu Mar  5 09:15:34 2015
From: holger at merlinux.eu (holger krekel)
Date: Thu, 5 Mar 2015 08:15:34 +0000
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CACTnz+FqoT43t81M5GiNjRFTycinJhr_TGUqSKgoWCG=YLdptA@mail.gmail.com>
References: <87k2yxrafj.fsf@hummelbi.lan>
 <CACTnz+FqoT43t81M5GiNjRFTycinJhr_TGUqSKgoWCG=YLdptA@mail.gmail.com>
Message-ID: <20150305081534.GI17945@merlinux.eu>

On Wed, Mar 04, 2015 at 09:20 +0100, Anatoly Bubenkov wrote:
> i suggest moving under pytest-dev as a first step (and add pypi access to
> at least 2 team members), without having an explicit maintainer

I disagree.  We should make sure that at least initially there is
some interest from people already in pytest-dev to maintain a plugin
if the author does not want to join himself.  Otherwise we end up with a
bunch of unmaintained plugins a bit too easily.

best,
holger


> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> 
> > Hi,
> >
> > pytest-twisted is a plugin for pytest, which allows to test code, which
> > uses the twisted framework.
> >
> > pytest-twisted needs a new maintainer. The code is on github [1], so I
> > think it would make sense to move it to the new pytest-dev organization.
> >
> > Is anyone interested in maintaining it and moving it over to the
> > pytest-dev organization?
> >
> > [1] https://github.com/schmir/pytest-twisted
> >
> > --
> > Cheers
> > Ralf
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
> 
> 
> 
> -- 
> Anatoly Bubenkov

> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From ralf at systemexit.de  Thu Mar  5 09:38:36 2015
From: ralf at systemexit.de (Ralf Schmitt)
Date: Thu, 05 Mar 2015 09:38:36 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <20150305081534.GI17945@merlinux.eu> (holger krekel's message of
 "Thu, 5 Mar 2015 08:15:34 +0000")
References: <87k2yxrafj.fsf@hummelbi.lan>
 <CACTnz+FqoT43t81M5GiNjRFTycinJhr_TGUqSKgoWCG=YLdptA@mail.gmail.com>
 <20150305081534.GI17945@merlinux.eu>
Message-ID: <87vbifet4j.fsf@rabbat.zvknet.intern>

holger krekel <holger at merlinux.eu> writes:

> On Wed, Mar 04, 2015 at 09:20 +0100, Anatoly Bubenkov wrote:
>> i suggest moving under pytest-dev as a first step (and add pypi access to
>> at least 2 team members), without having an explicit maintainer
>
> I disagree.  We should make sure that at least initially there is
> some interest from people already in pytest-dev to maintain a plugin
> if the author does not want to join himself.  Otherwise we end up with a
> bunch of unmaintained plugins a bit too easily.

ok, that's fine. I'm going to add a short note to the readme.  If anyone
wants to take over please contact me off list then.

-- 
Cheers
Ralf

From bubenkoff at gmail.com  Fri Mar  6 09:40:03 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Fri, 6 Mar 2015 09:40:03 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <20150305081534.GI17945@merlinux.eu>
References: <87k2yxrafj.fsf@hummelbi.lan>
 <CACTnz+FqoT43t81M5GiNjRFTycinJhr_TGUqSKgoWCG=YLdptA@mail.gmail.com>
 <20150305081534.GI17945@merlinux.eu>
Message-ID: <CACTnz+HTVAas8NZPFprsepKtr4fV3xtPk1LmQgB45G28epXTGw@mail.gmail.com>

I can't totally agree with this. pytest community is responsible anyway for
the pytest plugins whose original authors/maintainers want to resign.
And that was one of the main reason for me to push for the pytest-dev team
- the guarantee that even if the plugin's author doesn't work to do
anything for certain plugin anymore, the community will take over and will
at least do bugfix releases/merge PRs, this is not so much of work. And why
it's required to have explicit maintainer - it's not clear to me fully.
PS: pytest-twisted is actually useful and used by the people, so loosing it
is a bit sad

On 5 March 2015 at 09:15, holger krekel <holger at merlinux.eu> wrote:

> On Wed, Mar 04, 2015 at 09:20 +0100, Anatoly Bubenkov wrote:
> > i suggest moving under pytest-dev as a first step (and add pypi access to
> > at least 2 team members), without having an explicit maintainer
>
> I disagree.  We should make sure that at least initially there is
> some interest from people already in pytest-dev to maintain a plugin
> if the author does not want to join himself.  Otherwise we end up with a
> bunch of unmaintained plugins a bit too easily.
>
> best,
> holger
>
>
> > On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> >
> > > Hi,
> > >
> > > pytest-twisted is a plugin for pytest, which allows to test code, which
> > > uses the twisted framework.
> > >
> > > pytest-twisted needs a new maintainer. The code is on github [1], so I
> > > think it would make sense to move it to the new pytest-dev
> organization.
> > >
> > > Is anyone interested in maintaining it and moving it over to the
> > > pytest-dev organization?
> > >
> > > [1] https://github.com/schmir/pytest-twisted
> > >
> > > --
> > > Cheers
> > > Ralf
> > > _______________________________________________
> > > pytest-dev mailing list
> > > pytest-dev at python.org
> > > https://mail.python.org/mailman/listinfo/pytest-dev
> > >
> >
> >
> >
> > --
> > Anatoly Bubenkov
>
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150306/ccc39ad3/attachment.html>

From nicoddemus at gmail.com  Fri Mar  6 14:44:05 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 6 Mar 2015 10:44:05 -0300
Subject: [pytest-dev] PyCharm "skeletons" for pytest
Message-ID: <CA+RQFfcjRymvPPbYR759hRon+Yje1ExJsaOY8MZ95U+WERH82A@mail.gmail.com>

Hi all,

I've implemented PyCharm "skeletons" for pytest. Skeletons are hints to
PyCharm's auto-completion engine for modules that make heavy use of dynamic
declarations, such as pytest.

To install it, type:

cd $HOME/.PyCharm40/config
git clone https://github.com/nicoddemus/python-skeletons.git -b pytest

I have opened a PR for this to be incorporated into the official PyCharm
skeletons, but this was awhile ago so I thought I would mention it here so
others can make use of it while it is not merged.

Cheers,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150306/b72097c4/attachment.html>

From ralf at systemexit.de  Fri Mar  6 22:31:01 2015
From: ralf at systemexit.de (Ralf Schmitt)
Date: Fri, 06 Mar 2015 22:31:01 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CACTnz+HTVAas8NZPFprsepKtr4fV3xtPk1LmQgB45G28epXTGw@mail.gmail.com>
 (Anatoly Bubenkov's message of "Fri, 6 Mar 2015 09:40:03 +0100")
References: <87k2yxrafj.fsf@hummelbi.lan>
 <CACTnz+FqoT43t81M5GiNjRFTycinJhr_TGUqSKgoWCG=YLdptA@mail.gmail.com>
 <20150305081534.GI17945@merlinux.eu>
 <CACTnz+HTVAas8NZPFprsepKtr4fV3xtPk1LmQgB45G28epXTGw@mail.gmail.com>
Message-ID: <8761aderu2.fsf@hummelbi.lan>

Anatoly Bubenkov <bubenkoff at gmail.com> writes:

> I can't totally agree with this. pytest community is responsible anyway for
> the pytest plugins whose original authors/maintainers want to resign.
> And that was one of the main reason for me to push for the pytest-dev team
> - the guarantee that even if the plugin's author doesn't work to do
> anything for certain plugin anymore, the community will take over and will
> at least do bugfix releases/merge PRs, this is not so much of work. And why
> it's required to have explicit maintainer - it's not clear to me fully.

I agree with Anatoly's reasoning and I think it would not hurt to add
unmaintained packages. 

> PS: pytest-twisted is actually useful and used by the people, so loosing it
> is a bit sad

Christian Long volunteered to maintain pytest-twisted. The repository
already moved to https://github.com/christianmlong/pytest-twisted.
I hope that it can be added to the pytest-dev organization.

-- 
Cheers
Ralf

From bubenkoff at gmail.com  Fri Mar  6 22:34:54 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Fri, 6 Mar 2015 22:34:54 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <8761aderu2.fsf@hummelbi.lan>
References: <87k2yxrafj.fsf@hummelbi.lan>
 <CACTnz+FqoT43t81M5GiNjRFTycinJhr_TGUqSKgoWCG=YLdptA@mail.gmail.com>
 <20150305081534.GI17945@merlinux.eu>
 <CACTnz+HTVAas8NZPFprsepKtr4fV3xtPk1LmQgB45G28epXTGw@mail.gmail.com>
 <8761aderu2.fsf@hummelbi.lan>
Message-ID: <CACTnz+Ho5E2ZqNiXeL-=jZ2B_pbFz6UiQx6+=AdXP8w8g64vdw@mail.gmail.com>

respect!

On 6 March 2015 at 22:31, Ralf Schmitt <ralf at systemexit.de> wrote:

> Anatoly Bubenkov <bubenkoff at gmail.com> writes:
>
> > I can't totally agree with this. pytest community is responsible anyway
> for
> > the pytest plugins whose original authors/maintainers want to resign.
> > And that was one of the main reason for me to push for the pytest-dev
> team
> > - the guarantee that even if the plugin's author doesn't work to do
> > anything for certain plugin anymore, the community will take over and
> will
> > at least do bugfix releases/merge PRs, this is not so much of work. And
> why
> > it's required to have explicit maintainer - it's not clear to me fully.
>
> I agree with Anatoly's reasoning and I think it would not hurt to add
> unmaintained packages.
>
> > PS: pytest-twisted is actually useful and used by the people, so loosing
> it
> > is a bit sad
>
> Christian Long volunteered to maintain pytest-twisted. The repository
> already moved to https://github.com/christianmlong/pytest-twisted.
> I hope that it can be added to the pytest-dev organization.
>
> --
> Cheers
> Ralf
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150306/d513aaf8/attachment.html>

From christianzlong2 at gmail.com  Fri Mar  6 23:29:23 2015
From: christianzlong2 at gmail.com (Christian Long)
Date: Fri, 6 Mar 2015 16:29:23 -0600
Subject: [pytest-dev] pytest-twisted needs a new maintainer
Message-ID: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>

On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> pytest-twisted needs a new maintainer. The code is on github [1], so I
> think it would make sense to move it to the new pytest-dev organization.
>
> Is anyone interested in maintaining it and moving it over to the
> pytest-dev organization?

Hello,

My name is Christian Long. I'm new to the list, and I saw the call for
a maintainer for pytest-twisted. I have been working with Ralph to
take over maintenance on the pytest-twisted plugin.

I know a bit about Twisted, pytest and contributing to open source -
enough to get started.

So far, Ralph has given me ownership on PyPI and on github. However,
github won't allow me to transfer ownership to the pytest-dev
organization because I'm not an admin of pytest-dev.

The github docs have this to say:
https://help.github.com/articles/transferring-a-repository/

    If the user does not already have [admin or owner rights], a
    temporary admin team can be created with only the user.

So, we could do that, or I could transfer ownership of the github repo
to an existing pytest-dev admin who can then transfer it to the
organization.

Please let me know how you want to proceed.

Thank you for your help, and I look forward to working with you as the
new maintainer of pytest-twisted.

Christian Long

From bubenkoff at gmail.com  Fri Mar  6 23:32:48 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Fri, 6 Mar 2015 23:32:48 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
Message-ID: <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>

i vote for adding Christian and Ralf to the pytest-dev and acceping
pytest-twisted to the new home!

On 6 March 2015 at 23:29, Christian Long <christianzlong2 at gmail.com> wrote:

> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> > pytest-twisted needs a new maintainer. The code is on github [1], so I
> > think it would make sense to move it to the new pytest-dev organization.
> >
> > Is anyone interested in maintaining it and moving it over to the
> > pytest-dev organization?
>
> Hello,
>
> My name is Christian Long. I'm new to the list, and I saw the call for
> a maintainer for pytest-twisted. I have been working with Ralph to
> take over maintenance on the pytest-twisted plugin.
>
> I know a bit about Twisted, pytest and contributing to open source -
> enough to get started.
>
> So far, Ralph has given me ownership on PyPI and on github. However,
> github won't allow me to transfer ownership to the pytest-dev
> organization because I'm not an admin of pytest-dev.
>
> The github docs have this to say:
> https://help.github.com/articles/transferring-a-repository/
>
>     If the user does not already have [admin or owner rights], a
>     temporary admin team can be created with only the user.
>
> So, we could do that, or I could transfer ownership of the github repo
> to an existing pytest-dev admin who can then transfer it to the
> organization.
>
> Please let me know how you want to proceed.
>
> Thank you for your help, and I look forward to working with you as the
> new maintainer of pytest-twisted.
>
> Christian Long
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150306/97eca8bb/attachment.html>

From nicoddemus at gmail.com  Fri Mar  6 23:39:57 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 6 Mar 2015 19:39:57 -0300
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
 <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
Message-ID: <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>

I'm OK as well. :)

On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov <bubenkoff at gmail.com>
wrote:

> i vote for adding Christian and Ralf to the pytest-dev and acceping
> pytest-twisted to the new home!
>
> On 6 March 2015 at 23:29, Christian Long <christianzlong2 at gmail.com>
> wrote:
>
>> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
>> > pytest-twisted needs a new maintainer. The code is on github [1], so I
>> > think it would make sense to move it to the new pytest-dev organization.
>> >
>> > Is anyone interested in maintaining it and moving it over to the
>> > pytest-dev organization?
>>
>> Hello,
>>
>> My name is Christian Long. I'm new to the list, and I saw the call for
>> a maintainer for pytest-twisted. I have been working with Ralph to
>> take over maintenance on the pytest-twisted plugin.
>>
>> I know a bit about Twisted, pytest and contributing to open source -
>> enough to get started.
>>
>> So far, Ralph has given me ownership on PyPI and on github. However,
>> github won't allow me to transfer ownership to the pytest-dev
>> organization because I'm not an admin of pytest-dev.
>>
>> The github docs have this to say:
>> https://help.github.com/articles/transferring-a-repository/
>>
>>     If the user does not already have [admin or owner rights], a
>>     temporary admin team can be created with only the user.
>>
>> So, we could do that, or I could transfer ownership of the github repo
>> to an existing pytest-dev admin who can then transfer it to the
>> organization.
>>
>> Please let me know how you want to proceed.
>>
>> Thank you for your help, and I look forward to working with you as the
>> new maintainer of pytest-twisted.
>>
>> Christian Long
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
>
>
> --
> Anatoly Bubenkov
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150306/f9176238/attachment-0001.html>

From holger at merlinux.eu  Sat Mar  7 08:26:49 2015
From: holger at merlinux.eu (holger krekel)
Date: Sat, 7 Mar 2015 07:26:49 +0000
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
 <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
 <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>
Message-ID: <20150307072649.GB1676@merlinux.eu>

On Fri, Mar 06, 2015 at 19:39 -0300, Bruno Oliveira wrote:
> I'm OK as well. :)

me as well FWIW.  Hi Christian :)

holger

> On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov <bubenkoff at gmail.com>
> wrote:
> 
> > i vote for adding Christian and Ralf to the pytest-dev and acceping
> > pytest-twisted to the new home!
> >
> > On 6 March 2015 at 23:29, Christian Long <christianzlong2 at gmail.com>
> > wrote:
> >
> >> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> >> > pytest-twisted needs a new maintainer. The code is on github [1], so I
> >> > think it would make sense to move it to the new pytest-dev organization.
> >> >
> >> > Is anyone interested in maintaining it and moving it over to the
> >> > pytest-dev organization?
> >>
> >> Hello,
> >>
> >> My name is Christian Long. I'm new to the list, and I saw the call for
> >> a maintainer for pytest-twisted. I have been working with Ralph to
> >> take over maintenance on the pytest-twisted plugin.
> >>
> >> I know a bit about Twisted, pytest and contributing to open source -
> >> enough to get started.
> >>
> >> So far, Ralph has given me ownership on PyPI and on github. However,
> >> github won't allow me to transfer ownership to the pytest-dev
> >> organization because I'm not an admin of pytest-dev.
> >>
> >> The github docs have this to say:
> >> https://help.github.com/articles/transferring-a-repository/
> >>
> >>     If the user does not already have [admin or owner rights], a
> >>     temporary admin team can be created with only the user.
> >>
> >> So, we could do that, or I could transfer ownership of the github repo
> >> to an existing pytest-dev admin who can then transfer it to the
> >> organization.
> >>
> >> Please let me know how you want to proceed.
> >>
> >> Thank you for your help, and I look forward to working with you as the
> >> new maintainer of pytest-twisted.
> >>
> >> Christian Long
> >> _______________________________________________
> >> pytest-dev mailing list
> >> pytest-dev at python.org
> >> https://mail.python.org/mailman/listinfo/pytest-dev
> >>
> >
> >
> >
> > --
> > Anatoly Bubenkov
> >
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
> >

> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From bubenkoff at gmail.com  Sat Mar  7 10:46:27 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Sat, 7 Mar 2015 10:46:27 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <20150307072649.GB1676@merlinux.eu>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
 <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
 <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>
 <20150307072649.GB1676@merlinux.eu>
Message-ID: <CACTnz+FmsZeMpzVxwmpM=WXt4Uu9=OvU9qhem1j5Gbo8T3RpXg@mail.gmail.com>

I'll add you both - welcome!
On Mar 7, 2015 8:26 AM, "holger krekel" <holger at merlinux.eu> wrote:

> On Fri, Mar 06, 2015 at 19:39 -0300, Bruno Oliveira wrote:
> > I'm OK as well. :)
>
> me as well FWIW.  Hi Christian :)
>
> holger
>
> > On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov <bubenkoff at gmail.com>
> > wrote:
> >
> > > i vote for adding Christian and Ralf to the pytest-dev and acceping
> > > pytest-twisted to the new home!
> > >
> > > On 6 March 2015 at 23:29, Christian Long <christianzlong2 at gmail.com>
> > > wrote:
> > >
> > >> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> > >> > pytest-twisted needs a new maintainer. The code is on github [1],
> so I
> > >> > think it would make sense to move it to the new pytest-dev
> organization.
> > >> >
> > >> > Is anyone interested in maintaining it and moving it over to the
> > >> > pytest-dev organization?
> > >>
> > >> Hello,
> > >>
> > >> My name is Christian Long. I'm new to the list, and I saw the call for
> > >> a maintainer for pytest-twisted. I have been working with Ralph to
> > >> take over maintenance on the pytest-twisted plugin.
> > >>
> > >> I know a bit about Twisted, pytest and contributing to open source -
> > >> enough to get started.
> > >>
> > >> So far, Ralph has given me ownership on PyPI and on github. However,
> > >> github won't allow me to transfer ownership to the pytest-dev
> > >> organization because I'm not an admin of pytest-dev.
> > >>
> > >> The github docs have this to say:
> > >> https://help.github.com/articles/transferring-a-repository/
> > >>
> > >>     If the user does not already have [admin or owner rights], a
> > >>     temporary admin team can be created with only the user.
> > >>
> > >> So, we could do that, or I could transfer ownership of the github repo
> > >> to an existing pytest-dev admin who can then transfer it to the
> > >> organization.
> > >>
> > >> Please let me know how you want to proceed.
> > >>
> > >> Thank you for your help, and I look forward to working with you as the
> > >> new maintainer of pytest-twisted.
> > >>
> > >> Christian Long
> > >> _______________________________________________
> > >> pytest-dev mailing list
> > >> pytest-dev at python.org
> > >> https://mail.python.org/mailman/listinfo/pytest-dev
> > >>
> > >
> > >
> > >
> > > --
> > > Anatoly Bubenkov
> > >
> > > _______________________________________________
> > > pytest-dev mailing list
> > > pytest-dev at python.org
> > > https://mail.python.org/mailman/listinfo/pytest-dev
> > >
> > >
>
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150307/d9c42d3a/attachment.html>

From christianzlong2 at gmail.com  Sun Mar  8 23:21:35 2015
From: christianzlong2 at gmail.com (Christian Long)
Date: Sun, 8 Mar 2015 17:21:35 -0500
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CACTnz+FmsZeMpzVxwmpM=WXt4Uu9=OvU9qhem1j5Gbo8T3RpXg@mail.gmail.com>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
 <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
 <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>
 <20150307072649.GB1676@merlinux.eu>
 <CACTnz+FmsZeMpzVxwmpM=WXt4Uu9=OvU9qhem1j5Gbo8T3RpXg@mail.gmail.com>
Message-ID: <CAP3KJdi2CbXgR=zJhrcR1rufD1Zt8OC+Sm+N7HQTRoA6jycNjg@mail.gmail.com>

Thank you all for the warm welcome!

In Github, even though I'm a member of the pytest-dev organization, I
don't have permission to transfer ownership of the pytest-twisted
repo.

I can transfer it to one of the admins, who can then transfer it on to
the organization.

Christian

On Sat, Mar 7, 2015 at 3:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com> wrote:
> I'll add you both - welcome!
>
> On Mar 7, 2015 8:26 AM, "holger krekel" <holger at merlinux.eu> wrote:
>>
>> On Fri, Mar 06, 2015 at 19:39 -0300, Bruno Oliveira wrote:
>> > I'm OK as well. :)
>>
>> me as well FWIW.  Hi Christian :)
>>
>> holger
>>
>> > On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov <bubenkoff at gmail.com>
>> > wrote:
>> >
>> > > i vote for adding Christian and Ralf to the pytest-dev and acceping
>> > > pytest-twisted to the new home!
>> > >
>> > > On 6 March 2015 at 23:29, Christian Long <christianzlong2 at gmail.com>
>> > > wrote:
>> > >
>> > >> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
>> > >> > pytest-twisted needs a new maintainer. The code is on github [1],
>> > >> > so I
>> > >> > think it would make sense to move it to the new pytest-dev
>> > >> > organization.
>> > >> >
>> > >> > Is anyone interested in maintaining it and moving it over to the
>> > >> > pytest-dev organization?
>> > >>
>> > >> Hello,
>> > >>
>> > >> My name is Christian Long. I'm new to the list, and I saw the call
>> > >> for
>> > >> a maintainer for pytest-twisted. I have been working with Ralph to
>> > >> take over maintenance on the pytest-twisted plugin.
>> > >>
>> > >> I know a bit about Twisted, pytest and contributing to open source -
>> > >> enough to get started.
>> > >>
>> > >> So far, Ralph has given me ownership on PyPI and on github. However,
>> > >> github won't allow me to transfer ownership to the pytest-dev
>> > >> organization because I'm not an admin of pytest-dev.
>> > >>
>> > >> The github docs have this to say:
>> > >> https://help.github.com/articles/transferring-a-repository/
>> > >>
>> > >>     If the user does not already have [admin or owner rights], a
>> > >>     temporary admin team can be created with only the user.
>> > >>
>> > >> So, we could do that, or I could transfer ownership of the github
>> > >> repo
>> > >> to an existing pytest-dev admin who can then transfer it to the
>> > >> organization.
>> > >>
>> > >> Please let me know how you want to proceed.
>> > >>
>> > >> Thank you for your help, and I look forward to working with you as
>> > >> the
>> > >> new maintainer of pytest-twisted.
>> > >>
>> > >> Christian Long
>> > >> _______________________________________________
>> > >> pytest-dev mailing list
>> > >> pytest-dev at python.org
>> > >> https://mail.python.org/mailman/listinfo/pytest-dev
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > Anatoly Bubenkov
>> > >
>> > > _______________________________________________
>> > > pytest-dev mailing list
>> > > pytest-dev at python.org
>> > > https://mail.python.org/mailman/listinfo/pytest-dev
>> > >
>> > >
>>
>> > _______________________________________________
>> > pytest-dev mailing list
>> > pytest-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>> --
>> about me:    http://holgerkrekel.net/about-me/
>> contracting: http://merlinux.eu
>
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>

From bubenkoff at gmail.com  Mon Mar  9 08:31:16 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Mon, 9 Mar 2015 08:31:16 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CAP3KJdi2CbXgR=zJhrcR1rufD1Zt8OC+Sm+N7HQTRoA6jycNjg@mail.gmail.com>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
 <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
 <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>
 <20150307072649.GB1676@merlinux.eu>
 <CACTnz+FmsZeMpzVxwmpM=WXt4Uu9=OvU9qhem1j5Gbo8T3RpXg@mail.gmail.com>
 <CAP3KJdi2CbXgR=zJhrcR1rufD1Zt8OC+Sm+N7HQTRoA6jycNjg@mail.gmail.com>
Message-ID: <CACTnz+GWuPxjKp1ybVV5ez-fM=wAzRDb3NQafcZnj39OMNp0YQ@mail.gmail.com>

yes that's the way to go (unfortunately here github sucks comparing to bb),
please transfer to me (bubenkoff)

On 8 March 2015 at 23:21, Christian Long <christianzlong2 at gmail.com> wrote:

> Thank you all for the warm welcome!
>
> In Github, even though I'm a member of the pytest-dev organization, I
> don't have permission to transfer ownership of the pytest-twisted
> repo.
>
> I can transfer it to one of the admins, who can then transfer it on to
> the organization.
>
> Christian
>
> On Sat, Mar 7, 2015 at 3:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
> wrote:
> > I'll add you both - welcome!
> >
> > On Mar 7, 2015 8:26 AM, "holger krekel" <holger at merlinux.eu> wrote:
> >>
> >> On Fri, Mar 06, 2015 at 19:39 -0300, Bruno Oliveira wrote:
> >> > I'm OK as well. :)
> >>
> >> me as well FWIW.  Hi Christian :)
> >>
> >> holger
> >>
> >> > On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov <bubenkoff at gmail.com
> >
> >> > wrote:
> >> >
> >> > > i vote for adding Christian and Ralf to the pytest-dev and acceping
> >> > > pytest-twisted to the new home!
> >> > >
> >> > > On 6 March 2015 at 23:29, Christian Long <christianzlong2 at gmail.com
> >
> >> > > wrote:
> >> > >
> >> > >> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> >> > >> > pytest-twisted needs a new maintainer. The code is on github [1],
> >> > >> > so I
> >> > >> > think it would make sense to move it to the new pytest-dev
> >> > >> > organization.
> >> > >> >
> >> > >> > Is anyone interested in maintaining it and moving it over to the
> >> > >> > pytest-dev organization?
> >> > >>
> >> > >> Hello,
> >> > >>
> >> > >> My name is Christian Long. I'm new to the list, and I saw the call
> >> > >> for
> >> > >> a maintainer for pytest-twisted. I have been working with Ralph to
> >> > >> take over maintenance on the pytest-twisted plugin.
> >> > >>
> >> > >> I know a bit about Twisted, pytest and contributing to open source
> -
> >> > >> enough to get started.
> >> > >>
> >> > >> So far, Ralph has given me ownership on PyPI and on github.
> However,
> >> > >> github won't allow me to transfer ownership to the pytest-dev
> >> > >> organization because I'm not an admin of pytest-dev.
> >> > >>
> >> > >> The github docs have this to say:
> >> > >> https://help.github.com/articles/transferring-a-repository/
> >> > >>
> >> > >>     If the user does not already have [admin or owner rights], a
> >> > >>     temporary admin team can be created with only the user.
> >> > >>
> >> > >> So, we could do that, or I could transfer ownership of the github
> >> > >> repo
> >> > >> to an existing pytest-dev admin who can then transfer it to the
> >> > >> organization.
> >> > >>
> >> > >> Please let me know how you want to proceed.
> >> > >>
> >> > >> Thank you for your help, and I look forward to working with you as
> >> > >> the
> >> > >> new maintainer of pytest-twisted.
> >> > >>
> >> > >> Christian Long
> >> > >> _______________________________________________
> >> > >> pytest-dev mailing list
> >> > >> pytest-dev at python.org
> >> > >> https://mail.python.org/mailman/listinfo/pytest-dev
> >> > >>
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Anatoly Bubenkov
> >> > >
> >> > > _______________________________________________
> >> > > pytest-dev mailing list
> >> > > pytest-dev at python.org
> >> > > https://mail.python.org/mailman/listinfo/pytest-dev
> >> > >
> >> > >
> >>
> >> > _______________________________________________
> >> > pytest-dev mailing list
> >> > pytest-dev at python.org
> >> > https://mail.python.org/mailman/listinfo/pytest-dev
> >>
> >>
> >> --
> >> about me:    http://holgerkrekel.net/about-me/
> >> contracting: http://merlinux.eu
> >
> >
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150309/e0887da9/attachment.html>

From bubenkoff at gmail.com  Mon Mar  9 08:32:02 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Mon, 9 Mar 2015 08:32:02 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CAP3KJdi2CbXgR=zJhrcR1rufD1Zt8OC+Sm+N7HQTRoA6jycNjg@mail.gmail.com>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
 <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
 <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>
 <20150307072649.GB1676@merlinux.eu>
 <CACTnz+FmsZeMpzVxwmpM=WXt4Uu9=OvU9qhem1j5Gbo8T3RpXg@mail.gmail.com>
 <CAP3KJdi2CbXgR=zJhrcR1rufD1Zt8OC+Sm+N7HQTRoA6jycNjg@mail.gmail.com>
Message-ID: <CACTnz+FiP-fTbDVR=3gPWKbik4XOie9McxfrJG5znxOv5j0Ocw@mail.gmail.com>

stop, i just forgot to add you to the team properly, now it should be fine

On 8 March 2015 at 23:21, Christian Long <christianzlong2 at gmail.com> wrote:

> Thank you all for the warm welcome!
>
> In Github, even though I'm a member of the pytest-dev organization, I
> don't have permission to transfer ownership of the pytest-twisted
> repo.
>
> I can transfer it to one of the admins, who can then transfer it on to
> the organization.
>
> Christian
>
> On Sat, Mar 7, 2015 at 3:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
> wrote:
> > I'll add you both - welcome!
> >
> > On Mar 7, 2015 8:26 AM, "holger krekel" <holger at merlinux.eu> wrote:
> >>
> >> On Fri, Mar 06, 2015 at 19:39 -0300, Bruno Oliveira wrote:
> >> > I'm OK as well. :)
> >>
> >> me as well FWIW.  Hi Christian :)
> >>
> >> holger
> >>
> >> > On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov <bubenkoff at gmail.com
> >
> >> > wrote:
> >> >
> >> > > i vote for adding Christian and Ralf to the pytest-dev and acceping
> >> > > pytest-twisted to the new home!
> >> > >
> >> > > On 6 March 2015 at 23:29, Christian Long <christianzlong2 at gmail.com
> >
> >> > > wrote:
> >> > >
> >> > >> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de> wrote:
> >> > >> > pytest-twisted needs a new maintainer. The code is on github [1],
> >> > >> > so I
> >> > >> > think it would make sense to move it to the new pytest-dev
> >> > >> > organization.
> >> > >> >
> >> > >> > Is anyone interested in maintaining it and moving it over to the
> >> > >> > pytest-dev organization?
> >> > >>
> >> > >> Hello,
> >> > >>
> >> > >> My name is Christian Long. I'm new to the list, and I saw the call
> >> > >> for
> >> > >> a maintainer for pytest-twisted. I have been working with Ralph to
> >> > >> take over maintenance on the pytest-twisted plugin.
> >> > >>
> >> > >> I know a bit about Twisted, pytest and contributing to open source
> -
> >> > >> enough to get started.
> >> > >>
> >> > >> So far, Ralph has given me ownership on PyPI and on github.
> However,
> >> > >> github won't allow me to transfer ownership to the pytest-dev
> >> > >> organization because I'm not an admin of pytest-dev.
> >> > >>
> >> > >> The github docs have this to say:
> >> > >> https://help.github.com/articles/transferring-a-repository/
> >> > >>
> >> > >>     If the user does not already have [admin or owner rights], a
> >> > >>     temporary admin team can be created with only the user.
> >> > >>
> >> > >> So, we could do that, or I could transfer ownership of the github
> >> > >> repo
> >> > >> to an existing pytest-dev admin who can then transfer it to the
> >> > >> organization.
> >> > >>
> >> > >> Please let me know how you want to proceed.
> >> > >>
> >> > >> Thank you for your help, and I look forward to working with you as
> >> > >> the
> >> > >> new maintainer of pytest-twisted.
> >> > >>
> >> > >> Christian Long
> >> > >> _______________________________________________
> >> > >> pytest-dev mailing list
> >> > >> pytest-dev at python.org
> >> > >> https://mail.python.org/mailman/listinfo/pytest-dev
> >> > >>
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Anatoly Bubenkov
> >> > >
> >> > > _______________________________________________
> >> > > pytest-dev mailing list
> >> > > pytest-dev at python.org
> >> > > https://mail.python.org/mailman/listinfo/pytest-dev
> >> > >
> >> > >
> >>
> >> > _______________________________________________
> >> > pytest-dev mailing list
> >> > pytest-dev at python.org
> >> > https://mail.python.org/mailman/listinfo/pytest-dev
> >>
> >>
> >> --
> >> about me:    http://holgerkrekel.net/about-me/
> >> contracting: http://merlinux.eu
> >
> >
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150309/2fa8114f/attachment-0001.html>

From bubenkoff at gmail.com  Mon Mar  9 08:39:13 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Mon, 9 Mar 2015 08:39:13 +0100
Subject: [pytest-dev] pytest-twisted needs a new maintainer
In-Reply-To: <CACTnz+FiP-fTbDVR=3gPWKbik4XOie9McxfrJG5znxOv5j0Ocw@mail.gmail.com>
References: <CAP3KJdj0kfQXakt4BGUsuu4CCs9Dv0T-DFxgNNJCgAnmBTesGQ@mail.gmail.com>
 <CACTnz+Ef8i-uUj9qtmp8oBovkyqSRvauvrrpNb7SZT29s9AU6A@mail.gmail.com>
 <CA+RQFfdb72U+dHou8rPaE3d+-jYHPz32fkh=DekxMOCBAf5kqA@mail.gmail.com>
 <20150307072649.GB1676@merlinux.eu>
 <CACTnz+FmsZeMpzVxwmpM=WXt4Uu9=OvU9qhem1j5Gbo8T3RpXg@mail.gmail.com>
 <CAP3KJdi2CbXgR=zJhrcR1rufD1Zt8OC+Sm+N7HQTRoA6jycNjg@mail.gmail.com>
 <CACTnz+FiP-fTbDVR=3gPWKbik4XOie9McxfrJG5znxOv5j0Ocw@mail.gmail.com>
Message-ID: <CACTnz+G0XFwzpQXWxiMRoV0Q_bkjSgpi74LSk=-=aMNPYgmYdw@mail.gmail.com>

checked again, and you were added properly, it's just permission system of
github, which doesn't allow transfer without an admin access
so please transfer to me and then i'll transfer to the pytest-dev

On 9 March 2015 at 08:32, Anatoly Bubenkov <bubenkoff at gmail.com> wrote:

> stop, i just forgot to add you to the team properly, now it should be fine
>
> On 8 March 2015 at 23:21, Christian Long <christianzlong2 at gmail.com>
> wrote:
>
>> Thank you all for the warm welcome!
>>
>> In Github, even though I'm a member of the pytest-dev organization, I
>> don't have permission to transfer ownership of the pytest-twisted
>> repo.
>>
>> I can transfer it to one of the admins, who can then transfer it on to
>> the organization.
>>
>> Christian
>>
>> On Sat, Mar 7, 2015 at 3:46 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
>> wrote:
>> > I'll add you both - welcome!
>> >
>> > On Mar 7, 2015 8:26 AM, "holger krekel" <holger at merlinux.eu> wrote:
>> >>
>> >> On Fri, Mar 06, 2015 at 19:39 -0300, Bruno Oliveira wrote:
>> >> > I'm OK as well. :)
>> >>
>> >> me as well FWIW.  Hi Christian :)
>> >>
>> >> holger
>> >>
>> >> > On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov <
>> bubenkoff at gmail.com>
>> >> > wrote:
>> >> >
>> >> > > i vote for adding Christian and Ralf to the pytest-dev and acceping
>> >> > > pytest-twisted to the new home!
>> >> > >
>> >> > > On 6 March 2015 at 23:29, Christian Long <
>> christianzlong2 at gmail.com>
>> >> > > wrote:
>> >> > >
>> >> > >> On 3 March 2015 at 23:19, Ralf Schmitt <ralf at systemexit.de>
>> wrote:
>> >> > >> > pytest-twisted needs a new maintainer. The code is on github
>> [1],
>> >> > >> > so I
>> >> > >> > think it would make sense to move it to the new pytest-dev
>> >> > >> > organization.
>> >> > >> >
>> >> > >> > Is anyone interested in maintaining it and moving it over to the
>> >> > >> > pytest-dev organization?
>> >> > >>
>> >> > >> Hello,
>> >> > >>
>> >> > >> My name is Christian Long. I'm new to the list, and I saw the call
>> >> > >> for
>> >> > >> a maintainer for pytest-twisted. I have been working with Ralph to
>> >> > >> take over maintenance on the pytest-twisted plugin.
>> >> > >>
>> >> > >> I know a bit about Twisted, pytest and contributing to open
>> source -
>> >> > >> enough to get started.
>> >> > >>
>> >> > >> So far, Ralph has given me ownership on PyPI and on github.
>> However,
>> >> > >> github won't allow me to transfer ownership to the pytest-dev
>> >> > >> organization because I'm not an admin of pytest-dev.
>> >> > >>
>> >> > >> The github docs have this to say:
>> >> > >> https://help.github.com/articles/transferring-a-repository/
>> >> > >>
>> >> > >>     If the user does not already have [admin or owner rights], a
>> >> > >>     temporary admin team can be created with only the user.
>> >> > >>
>> >> > >> So, we could do that, or I could transfer ownership of the github
>> >> > >> repo
>> >> > >> to an existing pytest-dev admin who can then transfer it to the
>> >> > >> organization.
>> >> > >>
>> >> > >> Please let me know how you want to proceed.
>> >> > >>
>> >> > >> Thank you for your help, and I look forward to working with you as
>> >> > >> the
>> >> > >> new maintainer of pytest-twisted.
>> >> > >>
>> >> > >> Christian Long
>> >> > >> _______________________________________________
>> >> > >> pytest-dev mailing list
>> >> > >> pytest-dev at python.org
>> >> > >> https://mail.python.org/mailman/listinfo/pytest-dev
>> >> > >>
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Anatoly Bubenkov
>> >> > >
>> >> > > _______________________________________________
>> >> > > pytest-dev mailing list
>> >> > > pytest-dev at python.org
>> >> > > https://mail.python.org/mailman/listinfo/pytest-dev
>> >> > >
>> >> > >
>> >>
>> >> > _______________________________________________
>> >> > pytest-dev mailing list
>> >> > pytest-dev at python.org
>> >> > https://mail.python.org/mailman/listinfo/pytest-dev
>> >>
>> >>
>> >> --
>> >> about me:    http://holgerkrekel.net/about-me/
>> >> contracting: http://merlinux.eu
>> >
>> >
>> > _______________________________________________
>> > pytest-dev mailing list
>> > pytest-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>> >
>>
>
>
>
> --
> Anatoly Bubenkov
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150309/c97aeb98/attachment.html>

From brianna.laugher at gmail.com  Mon Mar  9 23:25:36 2015
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Mon, 9 Mar 2015 23:25:36 +0100
Subject: [pytest-dev] how to handle 'parameterize' misspelling
Message-ID: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>

Hello,

https://bitbucket.org/pytest-dev/pytest/issue/463/add-alias-for-parametrize-or-provide

It is, I think, a relatively common and easy error for someone to type
'pytest.mark.parameterize' instead of 'pytest.mark.parametrize'. At the
moment doing so (wrongly putting an extra 'e') results in an error like*
"fixture 'arg' not found" *which is not very revealing as to what the
problem actually is.

Two reasonable options would be
1) Treat parameterize as an alias of parametrize, so they behave identically
2) Check for the misspelling and raise a specific error about it

What are people's thoughts about the best approach?

cheers
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150309/7217c010/attachment.html>

From nicoddemus at gmail.com  Mon Mar  9 23:33:35 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 9 Mar 2015 19:33:35 -0300
Subject: [pytest-dev] how to handle 'parameterize' misspelling
In-Reply-To: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>
References: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>
Message-ID: <CA+RQFffcjyHUBWbPBzEyqZz_sT4rwqu7-Gg3Wf6azT4vnYZEHw@mail.gmail.com>

Hi Brianna,

Between the two options, I would go for option 2. I don't see much benefit
in an alias, as long as an early error warns the user about the mistake.

Wasn't there plans to eventually only allow users to use marks previously
declared, instead of generating them dynamically while accessing
`pytest.mark`?

Cheers,

On Mon, Mar 9, 2015 at 7:25 PM, Brianna Laugher <brianna.laugher at gmail.com>
wrote:

> Hello,
>
>
> https://bitbucket.org/pytest-dev/pytest/issue/463/add-alias-for-parametrize-or-provide
>
> It is, I think, a relatively common and easy error for someone to type
> 'pytest.mark.parameterize' instead of 'pytest.mark.parametrize'. At the
> moment doing so (wrongly putting an extra 'e') results in an error like*
> "fixture 'arg' not found" *which is not very revealing as to what the
> problem actually is.
>
> Two reasonable options would be
> 1) Treat parameterize as an alias of parametrize, so they behave
> identically
> 2) Check for the misspelling and raise a specific error about it
>
> What are people's thoughts about the best approach?
>
> cheers
> Brianna
>
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150309/9667625d/attachment.html>

From sandhu.jasmine at gmail.com  Mon Mar  9 23:37:46 2015
From: sandhu.jasmine at gmail.com (Jasmine Sandhu)
Date: Mon, 9 Mar 2015 15:37:46 -0700
Subject: [pytest-dev] how to handle 'parameterize' misspelling
In-Reply-To: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>
References: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>
Message-ID: <CAGeeQvZ68F5+OTJ04GxYjzdXVM3rX0qY0yZaDyaoR9KzAC4fLg@mail.gmail.com>

On Mon, Mar 9, 2015 at 3:25 PM, Brianna Laugher <brianna.laugher at gmail.com>
wrote:

> Hello,
>
>
> https://bitbucket.org/pytest-dev/pytest/issue/463/add-alias-for-parametrize-or-provide
>
> It is, I think, a relatively common and easy error for someone to type
> 'pytest.mark.parameterize' instead of 'pytest.mark.parametrize'. At the
> moment doing so (wrongly putting an extra 'e') results in an error like*
> "fixture 'arg' not found" *which is not very revealing as to what the
> problem actually is.
>
> Two reasonable options would be
> 1) Treat parameterize as an alias of parametrize, so they behave
> identically
> 2) Check for the misspelling and raise a specific error about it
>
> What are people's thoughts about the best approach?
>

I've done this many, many times though now I've used it enough to know what
to check for first when I see the error.

1) is easier on the user but better to have it spelled and used correctly
so perhaps 2) is better. Either way, this would be a good fix.

jasmine



>
> cheers
> Brianna
>
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150309/66d9fee2/attachment.html>

From holger at merlinux.eu  Tue Mar 10 10:26:43 2015
From: holger at merlinux.eu (holger krekel)
Date: Tue, 10 Mar 2015 09:26:43 +0000
Subject: [pytest-dev] how to handle 'parameterize' misspelling
In-Reply-To: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>
References: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>
Message-ID: <20150310092643.GE1676@merlinux.eu>

Hi Brianna,

On Mon, Mar 09, 2015 at 23:25 +0100, Brianna Laugher wrote:
> Hello,
> 
> https://bitbucket.org/pytest-dev/pytest/issue/463/add-alias-for-parametrize-or-provide
> 
> It is, I think, a relatively common and easy error for someone to type
> 'pytest.mark.parameterize' instead of 'pytest.mark.parametrize'. At the
> moment doing so (wrongly putting an extra 'e') results in an error like*
> "fixture 'arg' not found" *which is not very revealing as to what the
> problem actually is.
> 
> Two reasonable options would be
> 1) Treat parameterize as an alias of parametrize, so they behave identically
> 2) Check for the misspelling and raise a specific error about it
> 
> What are people's thoughts about the best approach?

For now 2) seems like a direct worthwhile fix/help to me.

FWIW I have a long-standing refactoring for markers which was at some point
95% complete (and discussed with Floris and others at a previous Pycon).
It would make registering markers much easier.  But waiting for it is
probably no the right strategy.

With the refactoring in place i'd feel more comfortable with issuing
warnings on non-registered markers.  Currently, marker registration
is a bit too clunky IMHO.

holger

From brianna.laugher at gmail.com  Tue Mar 10 12:38:19 2015
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Tue, 10 Mar 2015 12:38:19 +0100
Subject: [pytest-dev] how to handle 'parameterize' misspelling
In-Reply-To: <20150310092643.GE1676@merlinux.eu>
References: <CAPjwCjsRb+W1OnT680gX4nqqfPB+HjkCLRyt6qC4544TXAWnVg@mail.gmail.com>
 <20150310092643.GE1676@merlinux.eu>
Message-ID: <CAPjwCjuxZsacuL2NgDDAN3vsg-7VWfJTi8SRcya_WeRejCuJOA@mail.gmail.com>

Ok cool. I agree, as we don't know for sure when the registered-markers
thing will happen, this is still worth doing in the meantime.

Thanks
Brianna
On 10/03/2015 10:26 AM, "holger krekel" <holger at merlinux.eu> wrote:

> Hi Brianna,
>
> On Mon, Mar 09, 2015 at 23:25 +0100, Brianna Laugher wrote:
> > Hello,
> >
> >
> https://bitbucket.org/pytest-dev/pytest/issue/463/add-alias-for-parametrize-or-provide
> >
> > It is, I think, a relatively common and easy error for someone to type
> > 'pytest.mark.parameterize' instead of 'pytest.mark.parametrize'. At the
> > moment doing so (wrongly putting an extra 'e') results in an error like*
> > "fixture 'arg' not found" *which is not very revealing as to what the
> > problem actually is.
> >
> > Two reasonable options would be
> > 1) Treat parameterize as an alias of parametrize, so they behave
> identically
> > 2) Check for the misspelling and raise a specific error about it
> >
> > What are people's thoughts about the best approach?
>
> For now 2) seems like a direct worthwhile fix/help to me.
>
> FWIW I have a long-standing refactoring for markers which was at some point
> 95% complete (and discussed with Floris and others at a previous Pycon).
> It would make registering markers much easier.  But waiting for it is
> probably no the right strategy.
>
> With the refactoring in place i'd feel more comfortable with issuing
> warnings on non-registered markers.  Currently, marker registration
> is a bit too clunky IMHO.
>
> holger
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150310/06b0e723/attachment.html>

From tibor.arpas at infinit.sk  Fri Mar 13 16:39:20 2015
From: tibor.arpas at infinit.sk (Tibor Arpas)
Date: Fri, 13 Mar 2015 16:39:20 +0100
Subject: [pytest-dev] Crowdfunding a pytest plugin
In-Reply-To: <46C88FB1-F0FA-4AD3-B2E2-5285D438DABB@florian-schulze.net>
References: <CADi_WY2u4jD5H8MwoB0fXv1gi09fq38hnU9NPDHu4sYU8Z2juA@mail.gmail.com>
 <46C88FB1-F0FA-4AD3-B2E2-5285D438DABB@florian-schulze.net>
Message-ID: <CADi_WY2uYs+FRr6W6qdqxF0N+eRT13OCder1ssQCGERfDniSZA@mail.gmail.com>

Hi Florian

Longer ago you had some good points about selecting only tests affected by
recent changes as a basic functionality for our plugin - testmon.

We did more testing and thinking about these difficult questions and I
think they will not be that bad.


> I also thought about using something like coverage to only run affected
> tests. How much testing did you do in your prototype?


E.g. pytest test suite itself runs pretty nicely with testmon.


> Do you keep track of (pip/setuptools) installed packages (versions)?


Not yet, but I'm pretty sure a simple detection of changes under sys.path
that would trigger a full test run should be easy to implement and quick
enough.

Did you try changes at various levels like new files, modules, classes,
> metaclasses, mocks etc? Python is very dynamic as you most likely know :)
>

* files: sure
* modules, classes, metaclasses, mocks:
Unless I'm missing something this is not necessary. All of the dynamic
constructs are created deterministically in projects py files. If none of
the files involved in execution of a test is changed, then all of the
dynamic constructs will be the same in the next test run. Of course I might
be missing somethings, so if somebody has a good case please, let us know.

These things cause trouble for coveragepy (multiprocessing and gevent stuff
is beeing solved): http://nedbatchelder.com/code/coverage/trouble.html

These are my thoughts about the dependencies of a test:
https://github.com/tarpas/testmon#thoughts

Thanks for help,

Tibor
testmon - make your tests a breeze to execute http://igg.me/at/testmon


>
> Regards,
> Florian Schulze
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150313/47b55c65/attachment.html>

From bubenkoff at gmail.com  Thu Mar 19 14:11:40 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Thu, 19 Mar 2015 14:11:40 +0100
Subject: [pytest-dev] python hero is needed
Message-ID: <CACTnz+HwKZiQqjR5pkRhbOrC3tJcR0=uZJt363YXYJuyEGjk=Q@mail.gmail.com>

Hi

i know it can be considered harmful here,
but it's really related to the pytest (because we use pytest a lot and our
test setup is complicated)

so my company is looking for a senior engineer

http://careers.stackoverflow.com/jobs/82782/software-engineer-python-for-high-performance-paylogic-nederland-bv


-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150319/acc4d962/attachment.html>

From holger at merlinux.eu  Fri Mar 20 14:34:29 2015
From: holger at merlinux.eu (holger krekel)
Date: Fri, 20 Mar 2015 13:34:29 +0000
Subject: [pytest-dev] using discourse.org for pytest dev/proposals/ideas?
Message-ID: <20150320133429.GZ15735@merlinux.eu>


Today i hit some interesting software for discussions, "discourse.org",
on http://internals.rust-lang.org/

You can try it here:

    http://try.discourse.org/

Am wondering if we try to move proposals/feature/other discussions to
an instance of it at discuss.pytest.org or something.  What do you think?

best,
holger

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From bubenkoff at gmail.com  Fri Mar 20 15:03:39 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Fri, 20 Mar 2015 15:03:39 +0100
Subject: [pytest-dev] using discourse.org for pytest dev/proposals/ideas?
In-Reply-To: <20150320133429.GZ15735@merlinux.eu>
References: <20150320133429.GZ15735@merlinux.eu>
Message-ID: <CACTnz+GxuNaTummFx9ssBPsWCGqLWuyU_-qAmSErbX-O2b8D6g@mail.gmail.com>

Nice!
i like the github login :)

On 20 March 2015 at 14:34, holger krekel <holger at merlinux.eu> wrote:

>
> Today i hit some interesting software for discussions, "discourse.org",
> on http://internals.rust-lang.org/
>
> You can try it here:
>
>     http://try.discourse.org/
>
> Am wondering if we try to move proposals/feature/other discussions to
> an instance of it at discuss.pytest.org or something.  What do you think?
>
> best,
> holger
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150320/b83535cc/attachment.html>

From nicoddemus at gmail.com  Fri Mar 20 15:50:54 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 20 Mar 2015 11:50:54 -0300
Subject: [pytest-dev] using discourse.org for pytest dev/proposals/ideas?
In-Reply-To: <CACTnz+GxuNaTummFx9ssBPsWCGqLWuyU_-qAmSErbX-O2b8D6g@mail.gmail.com>
References: <20150320133429.GZ15735@merlinux.eu>
 <CACTnz+GxuNaTummFx9ssBPsWCGqLWuyU_-qAmSErbX-O2b8D6g@mail.gmail.com>
Message-ID: <CA+RQFfdfjhaj2cjq68mc_7c5qrnBtUTqFM3mFCET__cMuwVUAA@mail.gmail.com>

I see in the FAQ that Discourse and the mailing list have great overlapping
objectives (in fact Discourse aims to replace mailing lists).

The idea is to replace the mailing list? Or if not, which topics should be
discussed in the mailing list, and which ones should be discussed in
Discourse?

Cheers,

On Fri, Mar 20, 2015 at 11:03 AM, Anatoly Bubenkov <bubenkoff at gmail.com>
wrote:

> Nice!
> i like the github login :)
>
> On 20 March 2015 at 14:34, holger krekel <holger at merlinux.eu> wrote:
>
>>
>> Today i hit some interesting software for discussions, "discourse.org",
>> on http://internals.rust-lang.org/
>>
>> You can try it here:
>>
>>     http://try.discourse.org/
>>
>> Am wondering if we try to move proposals/feature/other discussions to
>> an instance of it at discuss.pytest.org or something.  What do you think?
>>
>> best,
>> holger
>>
>> --
>> about me:    http://holgerkrekel.net/about-me/
>> contracting: http://merlinux.eu
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
>
>
> --
> Anatoly Bubenkov
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150320/7f9788fa/attachment.html>

From holger at merlinux.eu  Mon Mar 23 10:23:18 2015
From: holger at merlinux.eu (holger krekel)
Date: Mon, 23 Mar 2015 09:23:18 +0000
Subject: [pytest-dev] get PRs ready for pytest-2.7 (to come this week)
Message-ID: <20150323092318.GX15735@merlinux.eu>

Hi all,

i'd like to get out pytest-2.7.0 out wednesday or thursday.  There are a few PRs hanging.
Please see to finalize/merge them.  I am not sure yet about the pytest-cache PR
and if it should get in so short ahead of a major release.  Maybe we can just
aim for a pytest-2.8 in April.

Speaking of PRs: if you start reviewing a PR and updates happen because of it please
aim for being the one to merge it or ask somebody else to do the merge.  
Some PRs are a bit too long lived for my taste :)

best,
holger

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From flub at devork.be  Tue Mar 24 10:09:19 2015
From: flub at devork.be (Floris Bruynooghe)
Date: Tue, 24 Mar 2015 09:09:19 +0000
Subject: [pytest-dev] using discourse.org for pytest dev/proposals/ideas?
In-Reply-To: <20150320133429.GZ15735@merlinux.eu>
References: <20150320133429.GZ15735@merlinux.eu>
Message-ID: <CAAWk_DxzGPSn18A+Um-5O=CdAH35f85Ek7uzDg4gYZtB=V6xvw@mail.gmail.com>

On 20 March 2015 at 13:34, holger krekel <holger at merlinux.eu> wrote:
> Am wondering if we try to move proposals/feature/other discussions to
> an instance of it at discuss.pytest.org or something.  What do you think?

If proposals and features move there won't this be confusing to people
finding the project and the normal issue tracker?  I imagine most proposals
and feature requests would still end up on the bitbucket issue tracker and
we'd then be stuck with some features here and some there.  Or having to
migrate them or something.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150324/560f050a/attachment.html>

From holger at merlinux.eu  Tue Mar 24 13:35:33 2015
From: holger at merlinux.eu (holger krekel)
Date: Tue, 24 Mar 2015 12:35:33 +0000
Subject: [pytest-dev] [Pytest-commit] commit/pytest: bubenkoff: add
 verbosity to the tests
In-Reply-To: <20150324105148.15416.93040@app10.ash-private.bitbucket.org>
References: <20150324105148.15416.93040@app10.ash-private.bitbucket.org>
Message-ID: <20150324123533.GB15996@merlinux.eu>

Hi Anatoly,

below, you directly changed the default for pytest to use verbose reporting.  I disagree
on it being the default as i almost never use verbose reporting expect in special
cases where it is then easy enough to use "-v".  So please revert.

We can think about integrating some "per-user" options which are stored in
a home directory if you like.

holger


On Tue, Mar 24, 2015 at 10:51 -0000, commits-noreply at bitbucket.org wrote:

> 1 new commit in pytest:
> 
> https://bitbucket.org/pytest-dev/pytest/commits/1146780cad2a/
> Changeset:   1146780cad2a
> User:        bubenkoff
> Date:        2015-03-24 10:51:45+00:00
> Summary:     add verbosity to the tests
> Affected #:  1 file
> 
> diff -r 9ad1ea7f3e905e6b89e613c30d17bd3c250e719f -r 1146780cad2a517cfca1e39e451db677533ac4e3 tox.ini
> --- a/tox.ini
> +++ b/tox.ini
> @@ -136,7 +136,7 @@
>  minversion=2.0
>  plugins=pytester
>  #--pyargs --doctest-modules --ignore=.tox
> -addopts= -rxsX 
> +addopts= -rxsXvl 
>  rsyncdirs=tox.ini pytest.py _pytest testing
>  python_files=test_*.py *_test.py testing/*/*.py
>  python_classes=Test Acceptance
> 
> Repository URL: https://bitbucket.org/pytest-dev/pytest/
> 
> --
> 
> This is a commit notification from bitbucket.org. You are receiving
> this because you have the service enabled, addressing the recipient of
> this email.
> _______________________________________________
> pytest-commit mailing list
> pytest-commit at python.org
> https://mail.python.org/mailman/listinfo/pytest-commit
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From bubenkoff at gmail.com  Tue Mar 24 13:40:35 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Tue, 24 Mar 2015 13:40:35 +0100
Subject: [pytest-dev] [Pytest-commit] commit/pytest: bubenkoff: add
 verbosity to the tests
In-Reply-To: <20150324123533.GB15996@merlinux.eu>
References: <20150324105148.15416.93040@app10.ash-private.bitbucket.org>
 <20150324123533.GB15996@merlinux.eu>
Message-ID: <CACTnz+GTpkiX=WZXd_Ey4AmEdQVT+teEtufJ1G3Ph5TVXw00mQ@mail.gmail.com>

my bad, sorry, i'll fix ASAP

On 24 March 2015 at 13:35, holger krekel <holger at merlinux.eu> wrote:

> Hi Anatoly,
>
> below, you directly changed the default for pytest to use verbose
> reporting.  I disagree
> on it being the default as i almost never use verbose reporting expect in
> special
> cases where it is then easy enough to use "-v".  So please revert.
>
> We can think about integrating some "per-user" options which are stored in
> a home directory if you like.
>
> holger
>
>
> On Tue, Mar 24, 2015 at 10:51 -0000, commits-noreply at bitbucket.org wrote:
>
> > 1 new commit in pytest:
> >
> > https://bitbucket.org/pytest-dev/pytest/commits/1146780cad2a/
> > Changeset:   1146780cad2a
> > User:        bubenkoff
> > Date:        2015-03-24 10:51:45+00:00
> > Summary:     add verbosity to the tests
> > Affected #:  1 file
> >
> > diff -r 9ad1ea7f3e905e6b89e613c30d17bd3c250e719f -r
> 1146780cad2a517cfca1e39e451db677533ac4e3 tox.ini
> > --- a/tox.ini
> > +++ b/tox.ini
> > @@ -136,7 +136,7 @@
> >  minversion=2.0
> >  plugins=pytester
> >  #--pyargs --doctest-modules --ignore=.tox
> > -addopts= -rxsX
> > +addopts= -rxsXvl
> >  rsyncdirs=tox.ini pytest.py _pytest testing
> >  python_files=test_*.py *_test.py testing/*/*.py
> >  python_classes=Test Acceptance
> >
> > Repository URL: https://bitbucket.org/pytest-dev/pytest/
> >
> > --
> >
> > This is a commit notification from bitbucket.org. You are receiving
> > this because you have the service enabled, addressing the recipient of
> > this email.
> > _______________________________________________
> > pytest-commit mailing list
> > pytest-commit at python.org
> > https://mail.python.org/mailman/listinfo/pytest-commit
> >
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150324/915bfdf7/attachment.html>

From brianna.laugher at gmail.com  Wed Mar 25 17:20:48 2015
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Wed, 25 Mar 2015 17:20:48 +0100
Subject: [pytest-dev] Website sidebar links are out of date
Message-ID: <CAPjwCjtLLr8nOtnA1E0_o7XDiJh2XF=imDZ5xqAxLq+AeEMk9g@mail.gmail.com>

Hi,

I noticed that the issue tracker and source links on the website are
linking to hpk42 rather than pytest-dev. It's worse for the issue
tracker as it just has a 404 and no link or information about the
moved repo.

I see the links were corrected already here
https://bitbucket.org/pytest-dev/pytest/pull-request/261/update-website-sidebar-links-for-repo-move/diff
- is it just waiting for a docs push or did something else happen?

Brianna

-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/

From bubenkoff at gmail.com  Wed Mar 25 17:22:27 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Wed, 25 Mar 2015 17:22:27 +0100
Subject: [pytest-dev] Website sidebar links are out of date
In-Reply-To: <CAPjwCjtLLr8nOtnA1E0_o7XDiJh2XF=imDZ5xqAxLq+AeEMk9g@mail.gmail.com>
References: <CAPjwCjtLLr8nOtnA1E0_o7XDiJh2XF=imDZ5xqAxLq+AeEMk9g@mail.gmail.com>
Message-ID: <CACTnz+GsCGQjqGdJJn4XPuXByDUTBZ3eeDK3U68K8TfsTLZrVQ@mail.gmail.com>

it's waiting for a next release, i guess

On 25 March 2015 at 17:20, Brianna Laugher <brianna.laugher at gmail.com>
wrote:

> Hi,
>
> I noticed that the issue tracker and source links on the website are
> linking to hpk42 rather than pytest-dev. It's worse for the issue
> tracker as it just has a 404 and no link or information about the
> moved repo.
>
> I see the links were corrected already here
>
> https://bitbucket.org/pytest-dev/pytest/pull-request/261/update-website-sidebar-links-for-repo-move/diff
> - is it just waiting for a docs push or did something else happen?
>
> Brianna
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150325/7bc5c6f8/attachment.html>

From holger at merlinux.eu  Wed Mar 25 18:01:56 2015
From: holger at merlinux.eu (holger krekel)
Date: Wed, 25 Mar 2015 17:01:56 +0000
Subject: [pytest-dev] Website sidebar links are out of date
In-Reply-To: <CAPjwCjtLLr8nOtnA1E0_o7XDiJh2XF=imDZ5xqAxLq+AeEMk9g@mail.gmail.com>
References: <CAPjwCjtLLr8nOtnA1E0_o7XDiJh2XF=imDZ5xqAxLq+AeEMk9g@mail.gmail.com>
Message-ID: <20150325170155.GC15735@merlinux.eu>

Hi Brianna,

thanks for noting.  I just pushed out the docs once again.  I am aware that the docs
should be pushed to http://pytest.org/dev instead of http://pytest.org/latest
and we should make sure that after the release we do this.  It means
that if we have pure doc fixes we need to apply them both to trunk
and the upcoming pytest-2.7 maintenance branch.

best,
holger


On Wed, Mar 25, 2015 at 17:20 +0100, Brianna Laugher wrote:
> Hi,
> 
> I noticed that the issue tracker and source links on the website are
> linking to hpk42 rather than pytest-dev. It's worse for the issue
> tracker as it just has a 404 and no link or information about the
> moved repo.
> 
> I see the links were corrected already here
> https://bitbucket.org/pytest-dev/pytest/pull-request/261/update-website-sidebar-links-for-repo-move/diff
> - is it just waiting for a docs push or did something else happen?
> 
> Brianna
> 
> -- 
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From holger at merlinux.eu  Thu Mar 26 09:38:10 2015
From: holger at merlinux.eu (holger krekel)
Date: Thu, 26 Mar 2015 08:38:10 +0000
Subject: [pytest-dev] pytest-2.7.0 release package / please test
Message-ID: <20150326083810.GE15735@merlinux.eu>

Hi everybody,

You can install either form trunk or with:

  pip install https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz

Please install it and work with it today and let me know any issues, regressions. 
I am going to release it verbatim this afternoon otherwise.

thanks,
holger

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From bubenkoff at gmail.com  Thu Mar 26 10:25:03 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Thu, 26 Mar 2015 10:25:03 +0100
Subject: [pytest-dev] pytest-2.7.0 release package / please test
In-Reply-To: <20150326083810.GE15735@merlinux.eu>
References: <20150326083810.GE15735@merlinux.eu>
Message-ID: <CACTnz+G2zOQauDz5Cv=tz0DNb55gzQydg3MJNqKT6jJ90iT=Cg@mail.gmail.com>

thanks!

works fine so far

On 26 March 2015 at 09:38, holger krekel <holger at merlinux.eu> wrote:

> Hi everybody,
>
> You can install either form trunk or with:
>
>   pip install
> https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz
>
> Please install it and work with it today and let me know any issues,
> regressions.
> I am going to release it verbatim this afternoon otherwise.
>
> thanks,
> holger
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150326/97497298/attachment.html>

From andreas at pelme.se  Thu Mar 26 10:35:41 2015
From: andreas at pelme.se (Andreas Pelme)
Date: Thu, 26 Mar 2015 10:35:41 +0100
Subject: [pytest-dev] pytest-2.7.0 release package / please test
In-Reply-To: <20150326083810.GE15735@merlinux.eu>
References: <20150326083810.GE15735@merlinux.eu>
Message-ID: <AC77DADB-3C4C-467E-BD5C-A3CD73845542@pelme.se>


> On 26 mar 2015, at 09:38, holger krekel <holger at merlinux.eu> wrote:
> 
>  pip install https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz
> 
> Please install it and work with it today and let me know any issues, regressions. 
> I am going to release it verbatim this afternoon otherwise.


Thanks for copy-pasteable pip command, my test suite runs fine without any issues (with and without xdist). Looking forward to the release!

Cheers,
Andreas


From tibor.arpas at infinit.sk  Thu Mar 26 12:37:12 2015
From: tibor.arpas at infinit.sk (Tibor Arpas)
Date: Thu, 26 Mar 2015 12:37:12 +0100
Subject: [pytest-dev] pytest-2.7.0 release package / please test
In-Reply-To: <AC77DADB-3C4C-467E-BD5C-A3CD73845542@pelme.se>
References: <20150326083810.GE15735@merlinux.eu>
 <AC77DADB-3C4C-467E-BD5C-A3CD73845542@pelme.se>
Message-ID: <CADi_WY2=V_8ADLnGhV4L-vM+07SafJYFzN92=iz7mo8pG9+qSg@mail.gmail.com>

I also didn't notice any difference in my limited test.

On Thu, Mar 26, 2015 at 10:35 AM, Andreas Pelme <andreas at pelme.se> wrote:
>
>> On 26 mar 2015, at 09:38, holger krekel <holger at merlinux.eu> wrote:
>>
>>  pip install https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz
>>
>> Please install it and work with it today and let me know any issues, regressions.
>> I am going to release it verbatim this afternoon otherwise.
>
>
> Thanks for copy-pasteable pip command, my test suite runs fine without any issues (with and without xdist). Looking forward to the release!
>
> Cheers,
> Andreas
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From nicoddemus at gmail.com  Thu Mar 26 12:43:22 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 26 Mar 2015 08:43:22 -0300
Subject: [pytest-dev] pytest-2.7.0 release package / please test
In-Reply-To: <CADi_WY2=V_8ADLnGhV4L-vM+07SafJYFzN92=iz7mo8pG9+qSg@mail.gmail.com>
References: <20150326083810.GE15735@merlinux.eu>
 <AC77DADB-3C4C-467E-BD5C-A3CD73845542@pelme.se>
 <CADi_WY2=V_8ADLnGhV4L-vM+07SafJYFzN92=iz7mo8pG9+qSg@mail.gmail.com>
Message-ID: <CA+RQFffFrOJx8J52BGBXNxndbp8ua+Jkk2RD2csPcN_6iXe1og@mail.gmail.com>

Tested in a few projects here and everything seems fine too.

Cheers,

On Thu, Mar 26, 2015 at 8:37 AM, Tibor Arpas <tibor.arpas at infinit.sk> wrote:

> I also didn't notice any difference in my limited test.
>
> On Thu, Mar 26, 2015 at 10:35 AM, Andreas Pelme <andreas at pelme.se> wrote:
> >
> >> On 26 mar 2015, at 09:38, holger krekel <holger at merlinux.eu> wrote:
> >>
> >>  pip install
> https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz
> >>
> >> Please install it and work with it today and let me know any issues,
> regressions.
> >> I am going to release it verbatim this afternoon otherwise.
> >
> >
> > Thanks for copy-pasteable pip command, my test suite runs fine without
> any issues (with and without xdist). Looking forward to the release!
> >
> > Cheers,
> > Andreas
> >
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150326/bbf1a072/attachment.html>

From holger at merlinux.eu  Thu Mar 26 13:42:40 2015
From: holger at merlinux.eu (holger krekel)
Date: Thu, 26 Mar 2015 12:42:40 +0000
Subject: [pytest-dev] pytest-2.7.0: fixes, features and more speed
Message-ID: <20150326124240.GF15735@merlinux.eu>

pytest-2.7.0: fixes, features, speed improvements
===========================================================================

pytest is a mature Python testing tool with more than a 1100 tests
against itself, passing on many different interpreters and platforms.
This release is supposed to be drop-in compatible to 2.6.X.

See below for the changes and see docs at:

    http://pytest.org

As usual, you can upgrade from pypi via::

    pip install -U pytest

Thanks to all who contributed, among them:

    Anatoly Bubenkoff
    Floris Bruynooghe
    Brianna Laugher
    Eric Siegerman
    Daniel Hahler
    Ronny Pfannschmidt
    Charles Cloud
    Tom Viner
    Holger Peters
    Ldiary Translations
    almarklein

have fun,
holger krekel

2.7.0 (compared to 2.6.4)
-----------------------------

- fix issue435: make reload() work when assert rewriting is active.
  Thanks Daniel Hahler.

- fix issue616: conftest.py files and their contained fixutres are now
  properly considered for visibility, independently from the exact
  current working directory and test arguments that are used.
  Many thanks to Eric Siegerman and his PR235 which contains
  systematic tests for conftest visibility and now passes.
  This change also introduces the concept of a ``rootdir`` which
  is printed as a new pytest header and documented in the pytest
  customize web page.

- change reporting of "diverted" tests, i.e. tests that are collected
  in one file but actually come from another (e.g. when tests in a test class
  come from a base class in a different file).  We now show the nodeid
  and indicate via a postfix the other file.

- add ability to set command line options by environment variable PYTEST_ADDOPTS.

- added documentation on the new pytest-dev teams on bitbucket and
  github.  See https://pytest.org/latest/contributing.html .
  Thanks to Anatoly for pushing and initial work on this.

- fix issue650: new option ``--docttest-ignore-import-errors`` which
  will turn import errors in doctests into skips.  Thanks Charles Cloud
  for the complete PR.

- fix issue655: work around different ways that cause python2/3
  to leak sys.exc_info into fixtures/tests causing failures in 3rd party code

- fix issue615: assertion re-writing did not correctly escape % signs
  when formatting boolean operations, which tripped over mixing
  booleans with modulo operators.  Thanks to Tom Viner for the report,
  triaging and fix.

- implement issue351: add ability to specify parametrize ids as a callable
  to generate custom test ids.  Thanks Brianna Laugher for the idea and
  implementation.

- introduce and document new hookwrapper mechanism useful for plugins
  which want to wrap the execution of certain hooks for their purposes.
  This supersedes the undocumented ``__multicall__`` protocol which
  pytest itself and some external plugins use.  Note that pytest-2.8
  is scheduled to drop supporting the old ``__multicall__``
  and only support the hookwrapper protocol.

- majorly speed up invocation of plugin hooks

- use hookwrapper mechanism in builtin pytest plugins.

- add a doctest ini option for doctest flags, thanks Holger Peters.

- add note to docs that if you want to mark a parameter and the
  parameter is a callable, you also need to pass in a reason to disambiguate
  it from the "decorator" case.  Thanks Tom Viner.

- "python_classes" and "python_functions" options now support glob-patterns
 for test discovery, as discussed in issue600. Thanks Ldiary Translations.

- allow to override parametrized fixtures with non-parametrized ones and vice versa (bubenkoff).

- fix issue463: raise specific error for 'parameterize' misspelling (pfctdayelise).

- On failure, the ``sys.last_value``, ``sys.last_type`` and
  ``sys.last_traceback`` are set, so that a user can inspect the error
  via postmortem debugging (almarklein).

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From holger at merlinux.eu  Thu Mar 26 14:12:23 2015
From: holger at merlinux.eu (holger krekel)
Date: Thu, 26 Mar 2015 13:12:23 +0000
Subject: [pytest-dev] release checklist / de-monopolizing release process
Message-ID: <20150326131223.GG15735@merlinux.eu>

Hi committers and friends of pytest :)

to de-monopolize the knowledge of releasing pytest i just created
a PR with a first stab at a release checklist:

https://bitbucket.org/pytest-dev/pytest/pull-request/266/add-a-release-checklist/diff

It doesn't explain how to use ``devpi``, maybe this tutorial helps:

    http://doc.devpi.net/latest/quickstart-releaseprocess.html

Ideally more of the release process would be automated, am open to PRs
and scripts doing it.

Also, i'd like to add some more people's SSH key to the "pytest-dev"
account on ``pytest.org``.  Brianna, Ronny and me can currently "make install"
the docs there.  Floris, Anatoly, Andreas, Bruno: please send me your public
ssh-key and your PYPI handle so you are technically able to do a release.
Anyone else who wants to and is in the current pytest-dev committer 
group is invited as well :)

best,
holger


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From holger at merlinux.eu  Thu Mar 26 14:23:23 2015
From: holger at merlinux.eu (holger krekel)
Date: Thu, 26 Mar 2015 13:23:23 +0000
Subject: [pytest-dev] release checklist / de-monopolizing release process
In-Reply-To: <20150326131223.GG15735@merlinux.eu>
References: <20150326131223.GG15735@merlinux.eu>
Message-ID: <20150326132323.GH15735@merlinux.eu>


One afterthought: i struggle a bit to find a good workflow especialy
related to docs.  

There are some changes to the docs which are release independent,
for example updating the current header info for "Adopt pytest month".

And there are changes which go together with not yet released code changes.

If we assume that pytest-2.7.X will be "bugfix only" we could
tie its doc target to "latest" and ask everybody who does doc enhancements
to target their PRs to "latest".

And for pytest-2.8 (trunk?) we'd put it to "dev".

This means that even little feature additions or changes in behaviour
would neccessarily need to go to pytest-2.8.  In the past, i have
allowed such little additions where i was pretty sure they wouldn't break
things into micro releases (working MAJOR.MINOR.MICRO naming here).

With pytest-2.7.0 a lot of the internal hook calling machinery changed
along with new hookwrapping mechanisms -- given the many plugins and
hook usages in test suites this is a bit of a risky change and therefore
i bumped the minor number.

Thoughts or opinions on this welcome.

Whatever we come up with, we may update "contributing.txt"
to reflect "PR targets".

best,
holger


On Thu, Mar 26, 2015 at 13:12 +0000, holger krekel wrote:
> Hi committers and friends of pytest :)
> 
> to de-monopolize the knowledge of releasing pytest i just created
> a PR with a first stab at a release checklist:
> 
> https://bitbucket.org/pytest-dev/pytest/pull-request/266/add-a-release-checklist/diff
> 
> It doesn't explain how to use ``devpi``, maybe this tutorial helps:
> 
>     http://doc.devpi.net/latest/quickstart-releaseprocess.html
> 
> Ideally more of the release process would be automated, am open to PRs
> and scripts doing it.
> 
> Also, i'd like to add some more people's SSH key to the "pytest-dev"
> account on ``pytest.org``.  Brianna, Ronny and me can currently "make install"
> the docs there.  Floris, Anatoly, Andreas, Bruno: please send me your public
> ssh-key and your PYPI handle so you are technically able to do a release.
> Anyone else who wants to and is in the current pytest-dev committer 
> group is invited as well :)
> 
> best,
> holger
> 
> 
> -- 
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From florian.schulze at gmx.net  Thu Mar 26 16:13:48 2015
From: florian.schulze at gmx.net (Florian Schulze)
Date: Thu, 26 Mar 2015 16:13:48 +0100
Subject: [pytest-dev] pytest-2.7.0 release package / please test
In-Reply-To: <20150326083810.GE15735@merlinux.eu>
References: <20150326083810.GE15735@merlinux.eu>
Message-ID: <ADC7F4B8-D090-45EC-AD66-552FC8CEABDB@gmx.net>

I tested a bit and had no issues so far.

Regards,
Florian Schulze


On 26 Mar 2015, at 9:38, holger krekel wrote:

> Hi everybody,
>
> You can install either form trunk or with:
>
> pip install 
> https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz
>
> Please install it and work with it today and let me know any issues, 
> regressions.
> I am going to release it verbatim this afternoon otherwise.
>
> thanks,
> holger
>
> -- 
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From christianzlong2 at gmail.com  Thu Mar 26 17:54:51 2015
From: christianzlong2 at gmail.com (Christian Long)
Date: Thu, 26 Mar 2015 11:54:51 -0500
Subject: [pytest-dev] pytest-2.7.0 release package / please test
In-Reply-To: <20150326083810.GE15735@merlinux.eu>
References: <20150326083810.GE15735@merlinux.eu>
Message-ID: <CAP3KJdiFfKad3nGi9Z-cu+YN2HxGDV0RfDx05zioOE61eShNvA@mail.gmail.com>

I ran my projects' tests with the new version and all was well.

On Thu, Mar 26, 2015 at 3:38 AM, holger krekel <holger at merlinux.eu> wrote:
> Hi everybody,
>
> You can install either form trunk or with:
>
>   pip install https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz
>
> Please install it and work with it today and let me know any issues, regressions.
> I am going to release it verbatim this afternoon otherwise.
>
> thanks,
> holger
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From nicoddemus at gmail.com  Thu Mar 26 23:12:31 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 26 Mar 2015 19:12:31 -0300
Subject: [pytest-dev] release checklist / de-monopolizing release process
In-Reply-To: <20150326132323.GH15735@merlinux.eu>
References: <20150326131223.GG15735@merlinux.eu>
 <20150326132323.GH15735@merlinux.eu>
Message-ID: <CA+RQFfe86yv-aeypBD8kUCYuh5ziUeGoFWLebubpUoYL6UEdoQ@mail.gmail.com>

Hi,

> If we assume that pytest-2.7.X will be "bugfix only" we could
> tie its doc target to "latest" and ask everybody who does doc enhancements
> to target their PRs to "latest".

Seems reasonable to me, but what about doc fixes for features which will
be released only on 2.8.0?

> This means that even little feature additions or changes in behaviour
> would neccessarily need to go to pytest-2.8. In the past, i have
> allowed such little additions where i was pretty sure they wouldn't break
> things into micro releases

According to Semantic Versioning, strictly speaking changes in existing
behavior would have to bump the minor number (except bugs, which would
bump MICRO). Not sure how people feel about it, but some
(myself included) like to know that they can safely update a library/tool
without having to review your code for usage changes (not that I've ever had
this problem with pytest, mind you). MAJOR should be updated for
backward-incompatible changes, but I don't see that happening anytime soon.

In the end of the day, I guess just having a couple of guidelines/rules in
place
is that everyone agrees on is good enough.

Back to which PRs should target, in "contributing.txt" it is recommended to
always target "latest". My knowledge of Mercurial is
limited so please correct me if I'm wrong, but doesn't that make it harder
to
port bug fixes to a "maintenance" branch?

Just to share what we have used in Git, maintenance branches are used
as targets for bug fixes, while master should be target for new features.
This way,
you can easily merge maintenance into master to port bug-fixes to the
future release,
while keeping a possible maintenance release free of new features.

Cheers,


On Thu, Mar 26, 2015 at 10:23 AM, holger krekel <holger at merlinux.eu> wrote:

>
> One afterthought: i struggle a bit to find a good workflow especialy
> related to docs.
>
> There are some changes to the docs which are release independent,
> for example updating the current header info for "Adopt pytest month".
>
> And there are changes which go together with not yet released code changes.
>
> If we assume that pytest-2.7.X will be "bugfix only" we could
> tie its doc target to "latest" and ask everybody who does doc enhancements
> to target their PRs to "latest".
>
> And for pytest-2.8 (trunk?) we'd put it to "dev".
>
> This means that even little feature additions or changes in behaviour
> would neccessarily need to go to pytest-2.8.  In the past, i have
> allowed such little additions where i was pretty sure they wouldn't break
> things into micro releases (working MAJOR.MINOR.MICRO naming here).
>
> With pytest-2.7.0 a lot of the internal hook calling machinery changed
> along with new hookwrapping mechanisms -- given the many plugins and
> hook usages in test suites this is a bit of a risky change and therefore
> i bumped the minor number.
>
> Thoughts or opinions on this welcome.
>
> Whatever we come up with, we may update "contributing.txt"
> to reflect "PR targets".
>
> best,
> holger
>
>
> On Thu, Mar 26, 2015 at 13:12 +0000, holger krekel wrote:
> > Hi committers and friends of pytest :)
> >
> > to de-monopolize the knowledge of releasing pytest i just created
> > a PR with a first stab at a release checklist:
> >
> >
> https://bitbucket.org/pytest-dev/pytest/pull-request/266/add-a-release-checklist/diff
> >
> > It doesn't explain how to use ``devpi``, maybe this tutorial helps:
> >
> >     http://doc.devpi.net/latest/quickstart-releaseprocess.html
> >
> > Ideally more of the release process would be automated, am open to PRs
> > and scripts doing it.
> >
> > Also, i'd like to add some more people's SSH key to the "pytest-dev"
> > account on ``pytest.org``.  Brianna, Ronny and me can currently "make
> install"
> > the docs there.  Floris, Anatoly, Andreas, Bruno: please send me your
> public
> > ssh-key and your PYPI handle so you are technically able to do a release.
> > Anyone else who wants to and is in the current pytest-dev committer
> > group is invited as well :)
> >
> > best,
> > holger
> >
> >
> > --
> > about me:    http://holgerkrekel.net/about-me/
> > contracting: http://merlinux.eu
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150326/6226af61/attachment.html>

From holger at merlinux.eu  Fri Mar 27 09:37:28 2015
From: holger at merlinux.eu (holger krekel)
Date: Fri, 27 Mar 2015 08:37:28 +0000
Subject: [pytest-dev] release checklist / de-monopolizing release process
In-Reply-To: <CA+RQFfe86yv-aeypBD8kUCYuh5ziUeGoFWLebubpUoYL6UEdoQ@mail.gmail.com>
References: <20150326131223.GG15735@merlinux.eu>
 <20150326132323.GH15735@merlinux.eu>
 <CA+RQFfe86yv-aeypBD8kUCYuh5ziUeGoFWLebubpUoYL6UEdoQ@mail.gmail.com>
Message-ID: <20150327083728.GO15735@merlinux.eu>

On Thu, Mar 26, 2015 at 19:12 -0300, Bruno Oliveira wrote:
> Hi,
> 
> > If we assume that pytest-2.7.X will be "bugfix only" we could
> > tie its doc target to "latest" and ask everybody who does doc enhancements
> > to target their PRs to "latest".
>
> Seems reasonable to me, but what about doc fixes for features which will
> be released only on 2.8.0?

Doc changes go to "dev" if they relate to a feature that is only in dev.

> > This means that even little feature additions or changes in behaviour
> > would neccessarily need to go to pytest-2.8. In the past, i have
> > allowed such little additions where i was pretty sure they wouldn't break
> > things into micro releases
> 
> According to Semantic Versioning, strictly speaking changes in existing
> behavior would have to bump the minor number (except bugs, which would
> bump MICRO). Not sure how people feel about it, but some
> (myself included) like to know that they can safely update a library/tool
> without having to review your code for usage changes (not that I've ever had
> this problem with pytest, mind you). MAJOR should be updated for
> backward-incompatible changes, but I don't see that happening anytime soon.
> 
> In the end of the day, I guess just having a couple of guidelines/rules in
> place
> is that everyone agrees on is good enough.

Note that virtually pytest releases are supposed to be backward compatible.
And even bug fixes can introduce backward compat problems.

> Back to which PRs should target, in "contributing.txt" it is recommended to
> always target "latest". My knowledge of Mercurial is
> limited so please correct me if I'm wrong, but doesn't that make it harder
> to
> port bug fixes to a "maintenance" branch?

Yes, i now changed CONTRIBUTING to differentiate between forking/merging
with ``default`` and ``pytest-VERSION-MAINTENANCE-branch``.  Indeed,
we should then regularly merge all bug fixes from the maintenance branch.

> Just to share what we have used in Git, maintenance branches are used
> as targets for bug fixes, while master should be target for new features.
> This way,
> you can easily merge maintenance into master to port bug-fixes to the
> future release,
> while keeping a possible maintenance release free of new features.

Yes, let's do it the same way.

I updated the pull request and also enhanced styling a bit to make code/literals
be more recognizable (the release doc was hard to read, otherwise).

Btw, what should this release-checklist PR be merged with?
I guess first with the maintenance version so that it goes to "pytest.org/latest"
and then also be ported to ``default``.  Sigh, this doc versioning
is a bit icky (which is why it was messed up in the past, pushing changes too early).

holger


> Cheers,
> 
> 
> On Thu, Mar 26, 2015 at 10:23 AM, holger krekel <holger at merlinux.eu> wrote:
> 
> >
> > One afterthought: i struggle a bit to find a good workflow especialy
> > related to docs.
> >
> > There are some changes to the docs which are release independent,
> > for example updating the current header info for "Adopt pytest month".
> >
> > And there are changes which go together with not yet released code changes.
> >
> > If we assume that pytest-2.7.X will be "bugfix only" we could
> > tie its doc target to "latest" and ask everybody who does doc enhancements
> > to target their PRs to "latest".
> >
> > And for pytest-2.8 (trunk?) we'd put it to "dev".
> >
> > This means that even little feature additions or changes in behaviour
> > would neccessarily need to go to pytest-2.8.  In the past, i have
> > allowed such little additions where i was pretty sure they wouldn't break
> > things into micro releases (working MAJOR.MINOR.MICRO naming here).
> >
> > With pytest-2.7.0 a lot of the internal hook calling machinery changed
> > along with new hookwrapping mechanisms -- given the many plugins and
> > hook usages in test suites this is a bit of a risky change and therefore
> > i bumped the minor number.
> >
> > Thoughts or opinions on this welcome.
> >
> > Whatever we come up with, we may update "contributing.txt"
> > to reflect "PR targets".
> >
> > best,
> > holger
> >
> >
> > On Thu, Mar 26, 2015 at 13:12 +0000, holger krekel wrote:
> > > Hi committers and friends of pytest :)
> > >
> > > to de-monopolize the knowledge of releasing pytest i just created
> > > a PR with a first stab at a release checklist:
> > >
> > >
> > https://bitbucket.org/pytest-dev/pytest/pull-request/266/add-a-release-checklist/diff
> > >
> > > It doesn't explain how to use ``devpi``, maybe this tutorial helps:
> > >
> > >     http://doc.devpi.net/latest/quickstart-releaseprocess.html
> > >
> > > Ideally more of the release process would be automated, am open to PRs
> > > and scripts doing it.
> > >
> > > Also, i'd like to add some more people's SSH key to the "pytest-dev"
> > > account on ``pytest.org``.  Brianna, Ronny and me can currently "make
> > install"
> > > the docs there.  Floris, Anatoly, Andreas, Bruno: please send me your
> > public
> > > ssh-key and your PYPI handle so you are technically able to do a release.
> > > Anyone else who wants to and is in the current pytest-dev committer
> > > group is invited as well :)
> > >
> > > best,
> > > holger
> > >
> > >
> > > --
> > > about me:    http://holgerkrekel.net/about-me/
> > > contracting: http://merlinux.eu
> > > _______________________________________________
> > > pytest-dev mailing list
> > > pytest-dev at python.org
> > > https://mail.python.org/mailman/listinfo/pytest-dev
> > >
> >
> > --
> > about me:    http://holgerkrekel.net/about-me/
> > contracting: http://merlinux.eu
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From tibor.arpas at infinit.sk  Fri Mar 27 15:55:31 2015
From: tibor.arpas at infinit.sk (Tibor Arpas)
Date: Fri, 27 Mar 2015 14:55:31 +0000
Subject: [pytest-dev] re-running pytest on file changes
Message-ID: <CADi_WY3cbDAOfDS8+oV5iRoF6qzvjsX+_PSmcBK-Ss1uObGCxA@mail.gmail.com>

Hi,

I'm trying to wrap my head around this subject.

Is there a strong reason why the -f looponfail option is inside a plug-in?
My hunch would be to do it as a separate, flexible, command, but that's
just feelings without any experience.

Poll: Do you guys use looponfail? Has it been working good? Does it play
nice with other tasks you might want to do on file changes? What other
tools do you use for repeated tasks on source code changes?

What's the situation at the moment with --looponfail and --looponchange? Is
it going to be inside pytest_cache which will go into core? Or it will be a
different plug-in?

I've seen
https://bitbucket.org/pytest-dev/pytest/commits/b5727cc6632c/

and the "take in cache" PR.


Tibor
P.S. some more thoughts about the same functionality are here:
https://github.com/tarpas/testmon/issues/4
and a script whith callbacks for every success and failure:
https://github.com/blueyed/testmon/blob/tmon-improvements/testmon/tmon.py
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150327/a09d699c/attachment.html>

From p-santoro at sbcglobal.net  Sat Mar 28 14:18:58 2015
From: p-santoro at sbcglobal.net (Peter)
Date: Sat, 28 Mar 2015 09:18:58 -0400
Subject: [pytest-dev] pytest-2.7.0 release package
Message-ID: <5516AA42.3000303@sbcglobal.net>

Outside of issue 701 that I reported just prior to the 2.7.0 release, I 
found no regressions in my usage of pytest (which I believe differs from 
the norm - see below).

I use python with pytest to check for observational equivalence between 
actual and expected results of a business critical C#.NET application. 
My conftest.py script customizes py.test with fixtures that automate the 
running of selected tests and their subsequent analysis. This includes 
the driving and coordination of CLI and GUI .NET applications that were 
not designed to support automated testing.  This automated test facility 
also includes a package to extend pytest's functionality.  For example:

- some fields (e.g. processing date) change with each run of the .NET 
application, which necessitates that certain fields in the actual and 
previously generated expected results are masked prior to using the 
built-in pytest assertions; I created a package to declaratively specify 
what fields are masked for various versioned record structures - the 
actual masking happens prior to using pytest assertions

- the record structures for this .NET application are required via 
legacy downstream systems and are at least 5000 bytes long; if there are 
only one or two differences between the actual and expected results and 
the differences are close together, the built-in pytest assertions 
produce a nice report; if there are multiple differences and they are 
far from each other, the built-in pytest assertion report isn't very 
helpful; I added functionality to produce a list of the indices where 
values differ, which greatly simplifies troubleshooting

The automated test facility that I built also includes a python 
application to automatically create automated test repository content 
for each test (i.e. test data, expected results, and the required 
py.test scripts).

The benefits of using pytest in this manner are as follows:

1) Creating good unit tests requires additional software development 
work - including testing the unit tests themselves.  That's fine, if you 
have sufficiently competent developers and the necessary time to do so. 
  The automated test facility that I built doesn't require any 
additional programming (beyond what I've already done); therefore, even 
business users and less experienced developers can create test data for 
use by the automated test system.

2) Supports rapid regression testing while refactoring the existing .NET 
code base.

3) Manual testing and analysis that often took days (sometimes weeks) 
can now be done in minutes.

4) Troubleshooting regression failures has been greatly simplified.


Thank you for producing a truly great piece of software!


Peter Santoro

From bubenkoff at gmail.com  Sat Mar 28 20:46:05 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Sat, 28 Mar 2015 20:46:05 +0100
Subject: [pytest-dev] pytest-2.7.0 release package
In-Reply-To: <5516AA42.3000303@sbcglobal.net>
References: <5516AA42.3000303@sbcglobal.net>
Message-ID: <CACTnz+GhMR6FSp6uYVyRbqDiME3QY6sFvcvMLDD-5SE2bFDKgQ@mail.gmail.com>

Thank you for sharing your experience!
Worth an article!
On Mar 28, 2015 6:23 PM, "Peter" <p-santoro at sbcglobal.net> wrote:

> Outside of issue 701 that I reported just prior to the 2.7.0 release, I
> found no regressions in my usage of pytest (which I believe differs from
> the norm - see below).
>
> I use python with pytest to check for observational equivalence between
> actual and expected results of a business critical C#.NET application. My
> conftest.py script customizes py.test with fixtures that automate the
> running of selected tests and their subsequent analysis. This includes the
> driving and coordination of CLI and GUI .NET applications that were not
> designed to support automated testing.  This automated test facility also
> includes a package to extend pytest's functionality.  For example:
>
> - some fields (e.g. processing date) change with each run of the .NET
> application, which necessitates that certain fields in the actual and
> previously generated expected results are masked prior to using the
> built-in pytest assertions; I created a package to declaratively specify
> what fields are masked for various versioned record structures - the actual
> masking happens prior to using pytest assertions
>
> - the record structures for this .NET application are required via legacy
> downstream systems and are at least 5000 bytes long; if there are only one
> or two differences between the actual and expected results and the
> differences are close together, the built-in pytest assertions produce a
> nice report; if there are multiple differences and they are far from each
> other, the built-in pytest assertion report isn't very helpful; I added
> functionality to produce a list of the indices where values differ, which
> greatly simplifies troubleshooting
>
> The automated test facility that I built also includes a python
> application to automatically create automated test repository content for
> each test (i.e. test data, expected results, and the required py.test
> scripts).
>
> The benefits of using pytest in this manner are as follows:
>
> 1) Creating good unit tests requires additional software development work
> - including testing the unit tests themselves.  That's fine, if you have
> sufficiently competent developers and the necessary time to do so.  The
> automated test facility that I built doesn't require any additional
> programming (beyond what I've already done); therefore, even business users
> and less experienced developers can create test data for use by the
> automated test system.
>
> 2) Supports rapid regression testing while refactoring the existing .NET
> code base.
>
> 3) Manual testing and analysis that often took days (sometimes weeks) can
> now be done in minutes.
>
> 4) Troubleshooting regression failures has been greatly simplified.
>
>
> Thank you for producing a truly great piece of software!
>
>
> Peter Santoro
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150328/510fc221/attachment.html>

From tom at viner.tv  Sun Mar 29 00:12:13 2015
From: tom at viner.tv (Tom Viner)
Date: Sat, 28 Mar 2015 23:12:13 +0000
Subject: [pytest-dev] re-running pytest on file changes
Message-ID: <CANBSuyG-zD=Y2byC8T5q7157vR08+xTKia+iPWuiOAQsdXPKhQ@mail.gmail.com>

I find it really helps TDD to have my tests run automatically whenever I
change either a test or the code itself. I set my editor (Sublime Text 3)
to auto save upon defocus, so it's actually impossible to avoid a test
rerun whenever I alter a file and move on or hit save.

For this, I regularly use Jonathan Hartley's rerun Python library[0] which
gives the ability to wrap my py.test or tox command like so:

rerun --ignore sqlite.db "py.test tests/"

The --ignore part is very important, as different test suites end up
altering various working directory files, and if you can't select
files/folders (file patterns would be even better) to ignore, you end up in
an un-pausing loop of test reruns.

I hadn't heard of looponchange can it ignore certain files/folders?

[0] https://pypi.python.org/pypi/rerun



> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 27 Mar 2015 14:55:31 +0000
> From: Tibor Arpas <tibor.arpas at infinit.sk>
> To: "pytest-dev at python.org" <pytest-dev at python.org>
> Subject: [pytest-dev] re-running pytest on file changes
> Message-ID:
>         <
> CADi_WY3cbDAOfDS8+oV5iRoF6qzvjsX+_PSmcBK-Ss1uObGCxA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I'm trying to wrap my head around this subject.
>
> Is there a strong reason why the -f looponfail option is inside a plug-in?
> My hunch would be to do it as a separate, flexible, command, but that's
> just feelings without any experience.
>
> Poll: Do you guys use looponfail? Has it been working good? Does it play
> nice with other tasks you might want to do on file changes? What other
> tools do you use for repeated tasks on source code changes?
>
> What's the situation at the moment with --looponfail and --looponchange? Is
> it going to be inside pytest_cache which will go into core? Or it will be a
> different plug-in?
>
> I've seen
> https://bitbucket.org/pytest-dev/pytest/commits/b5727cc6632c/
>
> and the "take in cache" PR.
>
>
> Tibor
> P.S. some more thoughts about the same functionality are here:
> https://github.com/tarpas/testmon/issues/4
> and a script whith callbacks for every success and failure:
> https://github.com/blueyed/testmon/blob/tmon-improvements/testmon/tmon.py
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/pytest-dev/attachments/20150327/a09d699c/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
> ------------------------------
>
> End of pytest-dev Digest, Vol 28, Issue 22
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150328/4297de10/attachment-0001.html>

From holger at merlinux.eu  Mon Mar 30 09:20:26 2015
From: holger at merlinux.eu (holger krekel)
Date: Mon, 30 Mar 2015 07:20:26 +0000
Subject: [pytest-dev] pytest-2.7.0 release package
In-Reply-To: <5516AA42.3000303@sbcglobal.net>
References: <5516AA42.3000303@sbcglobal.net>
Message-ID: <20150330072026.GW15735@merlinux.eu>

Hi Peter,

thanks for the description of your usage.  I'd be interested
in an example test and usage of the helpers you have created.

FWIW pytest itself has internal helpers for comparing expected
output and actual output of running pytest using wildcards
to mask out parts which are not interesting.  But those are
pretty much tied to string output rather than structs or records.

holger

On Sat, Mar 28, 2015 at 09:18 -0400, Peter wrote:
> Outside of issue 701 that I reported just prior to the 2.7.0
> release, I found no regressions in my usage of pytest (which I
> believe differs from the norm - see below).
> 
> I use python with pytest to check for observational equivalence
> between actual and expected results of a business critical C#.NET
> application. My conftest.py script customizes py.test with fixtures
> that automate the running of selected tests and their subsequent
> analysis. This includes the driving and coordination of CLI and GUI
> .NET applications that were not designed to support automated
> testing.  This automated test facility also includes a package to
> extend pytest's functionality.  For example:
> 
> - some fields (e.g. processing date) change with each run of the
> .NET application, which necessitates that certain fields in the
> actual and previously generated expected results are masked prior to
> using the built-in pytest assertions; I created a package to
> declaratively specify what fields are masked for various versioned
> record structures - the actual masking happens prior to using pytest
> assertions
> 
> - the record structures for this .NET application are required via
> legacy downstream systems and are at least 5000 bytes long; if there
> are only one or two differences between the actual and expected
> results and the differences are close together, the built-in pytest
> assertions produce a nice report; if there are multiple differences
> and they are far from each other, the built-in pytest assertion
> report isn't very helpful; I added functionality to produce a list
> of the indices where values differ, which greatly simplifies
> troubleshooting
> 
> The automated test facility that I built also includes a python
> application to automatically create automated test repository
> content for each test (i.e. test data, expected results, and the
> required py.test scripts).
> 
> The benefits of using pytest in this manner are as follows:
> 
> 1) Creating good unit tests requires additional software development
> work - including testing the unit tests themselves.  That's fine, if
> you have sufficiently competent developers and the necessary time to
> do so.  The automated test facility that I built doesn't require any
> additional programming (beyond what I've already done); therefore,
> even business users and less experienced developers can create test
> data for use by the automated test system.
> 
> 2) Supports rapid regression testing while refactoring the existing
> .NET code base.
> 
> 3) Manual testing and analysis that often took days (sometimes
> weeks) can now be done in minutes.
> 
> 4) Troubleshooting regression failures has been greatly simplified.
> 
> 
> Thank you for producing a truly great piece of software!
> 
> 
> Peter Santoro
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Tue Mar 31 12:10:04 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 31 Mar 2015 10:10:04 -0000
Subject: [pytest-dev] Move pytest-faulthandler to pytest-dev@github
Message-ID: <20150317102333.19571.29131@domU-12-31-39-0A-A0-4F>

Hi all,

I would to like to know if there are any objections to moving the 
pytest-faulthandler (https://github.com/nicoddemus/pytest-faulthandler) 
plugin to the pytest-dev at github organization?

Cheers,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150331/b93f14c2/attachment.html>

From tibor.arpas at infinit.sk  Tue Mar 31 16:20:37 2015
From: tibor.arpas at infinit.sk (Tibor Arpas)
Date: Tue, 31 Mar 2015 16:20:37 +0200
Subject: [pytest-dev] pytest, or pytest plug-in dogfooding
Message-ID: <CADi_WY3aj67mmHLM_xiWusm9pP-eLnCQ64q891ih0ED221BP_Q@mail.gmail.com>

Hi,
is it difficult to set-up development environment for hacking on
pytest itself or a plug-in where you use a stable version as a test
runner but the code under test is a different one?

Or in other words 'import pytest_myplugin' has to pick up the stable
source code on pytest start-up, but all the tests (and their
subprocesses)  doing 'import pytest_myplugin' have to pick-up the
bleading edge-version.

Thanks!
Tibor

From flub at devork.be  Tue Mar 31 17:01:22 2015
From: flub at devork.be (Floris Bruynooghe)
Date: Tue, 31 Mar 2015 16:01:22 +0100
Subject: [pytest-dev] Move pytest-faulthandler to pytest-dev@github
In-Reply-To: <20150317102333.19571.29131@domU-12-31-39-0A-A0-4F>
References: <20150317102333.19571.29131@domU-12-31-39-0A-A0-4F>
Message-ID: <CAAWk_Dz5XgwkRjCydAxjNE8U8BMScPccMvNhShd-Lai_pw_gMw@mail.gmail.com>

Sounds good to me

On 31 March 2015 at 11:10, Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi all,
>
> I would to like to know if there are any objections to moving the
> pytest-faulthandler (https://github.com/nicoddemus/pytest-faulthandler)
> plugin to the pytest-dev at github organization?
>
> Cheers,
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150331/175b098f/attachment.html>

From flub at devork.be  Tue Mar 31 17:04:24 2015
From: flub at devork.be (Floris Bruynooghe)
Date: Tue, 31 Mar 2015 16:04:24 +0100
Subject: [pytest-dev] pytest, or pytest plug-in dogfooding
In-Reply-To: <CADi_WY3aj67mmHLM_xiWusm9pP-eLnCQ64q891ih0ED221BP_Q@mail.gmail.com>
References: <CADi_WY3aj67mmHLM_xiWusm9pP-eLnCQ64q891ih0ED221BP_Q@mail.gmail.com>
Message-ID: <CAAWk_Dy73J2bhhoTwKtu_-RMXngRQ2gMhNDduyC8sAANQAGOJQ@mail.gmail.com>

Hi Tibor,

On 31 March 2015 at 15:20, Tibor Arpas <tibor.arpas at infinit.sk> wrote:

> is it difficult to set-up development environment for hacking on
> pytest itself or a plug-in where you use a stable version as a test
> runner but the code under test is a different one?
>

Not really, assuming your current working directory is the plugin's:

- Create and activate a new virtualenv
- pip install pytest
- pip install -e .

For py.test itself you just need to install pytest itself as editable using
pip.  If in doubt see the CONTRIBUTING.rst file included with py.test.

Regards,
Floris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150331/011f9a30/attachment.html>

From bubenkoff at gmail.com  Tue Mar 31 17:18:37 2015
From: bubenkoff at gmail.com (Anatoly Bubenkov)
Date: Tue, 31 Mar 2015 17:18:37 +0200
Subject: [pytest-dev] Move pytest-faulthandler to pytest-dev@github
In-Reply-To: <20150317102333.19571.29131@domU-12-31-39-0A-A0-4F>
References: <20150317102333.19571.29131@domU-12-31-39-0A-A0-4F>
Message-ID: <CACTnz+H2=Pg=i3r0bmtAxMowwi6nY1x+cD-8fNydwhvLcfyfxQ@mail.gmail.com>

im positive, as always regarding the growth of the pytest-dev

On 31 March 2015 at 12:10, Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi all,
>
> I would to like to know if there are any objections to moving the
> pytest-faulthandler (https://github.com/nicoddemus/pytest-faulthandler)
> plugin to the pytest-dev at github organization?
>
> Cheers,
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>


-- 
Anatoly Bubenkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150331/70dc6840/attachment.html>

From nicoddemus at gmail.com  Tue Mar 31 17:22:48 2015
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 31 Mar 2015 12:22:48 -0300
Subject: [pytest-dev] Move pytest-faulthandler to pytest-dev@github
In-Reply-To: <CACTnz+H2=Pg=i3r0bmtAxMowwi6nY1x+cD-8fNydwhvLcfyfxQ@mail.gmail.com>
References: <20150317102333.19571.29131@domU-12-31-39-0A-A0-4F>
 <CACTnz+H2=Pg=i3r0bmtAxMowwi6nY1x+cD-8fNydwhvLcfyfxQ@mail.gmail.com>
Message-ID: <CA+RQFfd9gYaZUkCoNJx8PfcWHtidXxqV0GyCz0ZiqdkL95Shiw@mail.gmail.com>

OK, I?ll move it then.

Cheers,
?

On Tue, Mar 31, 2015 at 12:18 PM, Anatoly Bubenkov <bubenkoff at gmail.com>
wrote:

> im positive, as always regarding the growth of the pytest-dev
>
> On 31 March 2015 at 12:10, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>
>> Hi all,
>>
>> I would to like to know if there are any objections to moving the
>> pytest-faulthandler (https://github.com/nicoddemus/pytest-faulthandler)
>> plugin to the pytest-dev at github organization?
>>
>> Cheers,
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>
>
> --
> Anatoly Bubenkov
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150331/1b466b11/attachment-0001.html>