From dhunt at mozilla.com  Fri Jul  1 09:57:25 2016
From: dhunt at mozilla.com (Dave Hunt)
Date: Fri, 1 Jul 2016 14:57:25 +0100
Subject: [pytest-dev] Idea for reversing report options
Message-ID: <517118AD-DE5E-460A-9DB9-60375A0311B7@mozilla.com>

During the sprint the issue of how to reverse extra test summary options specified using -r came up. I?ve also just noticed that showing the warnings by default added a --disable-pytest-warnings command line option. I had a thought, and wanted to share in case it was a favourable alternative to additional command line options.

We could add a new character for -r such as ?c? and if this is present it would first clear all additional test summaries. So if the default was effectively -r fEw we could specify -r cpP to show only extra summaries for passed tests. What do you think?

Dave

From opensource at ronnypfannschmidt.de  Fri Jul  1 15:59:57 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Fri, 1 Jul 2016 21:59:57 +0200
Subject: [pytest-dev] Idea for reversing report options
In-Reply-To: <517118AD-DE5E-460A-9DB9-60375A0311B7@mozilla.com>
References: <517118AD-DE5E-460A-9DB9-60375A0311B7@mozilla.com>
Message-ID: <eed19d56-dc0b-b4b1-c136-12563d211cea@ronnypfannschmidt.de>

i would propose a long option to clear the reportchars list instead

we should not have more than one DSL for the cli args

having logic actions triggered by element actions of a append argument
would start that

-- Ronny

Am 01.07.2016 um 15:57 schrieb Dave Hunt:
> During the sprint the issue of how to reverse extra test summary options specified using -r came up. I?ve also just noticed that showing the warnings by default added a --disable-pytest-warnings command line option. I had a thought, and wanted to share in case it was a favourable alternative to additional command line options.
>
> We could add a new character for -r such as ?c? and if this is present it would first clear all additional test summaries. So if the default was effectively -r fEw we could specify -r cpP to show only extra summaries for passed tests. What do you think?
>
> Dave
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


From flub at devork.be  Mon Jul  4 06:03:11 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Mon, 4 Jul 2016 11:03:11 +0100
Subject: [pytest-dev] rewrite-plugins & AppVeyor
Message-ID: <CAAWk_DxY6hHx01vxr_49Ob0P6hF-NB2j5WSsCjWUPjaOEezVKA@mail.gmail.com>

Hello,

For the rewrite-plugins PR
(https://github.com/pytest-dev/pytest/pull/1641) the AppVeyor build
seems to have timed out but has no obvious failures.  Is AppVeyor
always this unreliable?  It means mergable PRs are marked as having
issues on the summary, and if you wait long enough they will probably
grow another conflict with the changelog or so.

So two questions:

- Can rewrite-plugins be merged before it conflicts again or does
anyone still spot issues with it?  I want to re-base the
reiterpret-removal on this once merged.

- Is AppVeyor reliable enough?  Maybe we can make it run fewer jobs so
it doesn't time out?


Floris

From me at the-compiler.org  Mon Jul  4 06:13:52 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 4 Jul 2016 12:13:52 +0200
Subject: [pytest-dev] rewrite-plugins & AppVeyor
In-Reply-To: <CAAWk_DxY6hHx01vxr_49Ob0P6hF-NB2j5WSsCjWUPjaOEezVKA@mail.gmail.com>
References: <CAAWk_DxY6hHx01vxr_49Ob0P6hF-NB2j5WSsCjWUPjaOEezVKA@mail.gmail.com>
Message-ID: <20160704101352.aqa3ceoijwxaevdi@tonks>

Hey,

* Floris Bruynooghe <flub at devork.be> [2016-07-04 11:03:11 +0100]:
> Hello,
> 
> For the rewrite-plugins PR
> (https://github.com/pytest-dev/pytest/pull/1641) the AppVeyor build
> seems to have timed out but has no obvious failures.  Is AppVeyor
> always this unreliable?  It means mergable PRs are marked as having
> issues on the summary, and if you wait long enough they will probably
> grow another conflict with the changelog or so.

This doesn't look like AppVeyor being unreliable, but just our
testsuite taking too long. If you look at the build history, many
builds took 50-59 minutes, the best case I could find was 38.

> - Can rewrite-plugins be merged before it conflicts again or does
> anyone still spot issues with it?  I want to re-base the
> reiterpret-removal on this once merged.

FWIW I'll re-run AppVeyor and hope it finishes in time this time.
I don't feel qualified enough to review the PR ;)

> - Is AppVeyor reliable enough?  Maybe we can make it run fewer jobs so
> it doesn't time out?

We probably should do that unless we can speed up our testsuite
somehow.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160704/172aa2b7/attachment.sig>

From flub at devork.be  Mon Jul  4 07:56:25 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Mon, 4 Jul 2016 12:56:25 +0100
Subject: [pytest-dev] Blog RSS invalid
Message-ID: <CAAWk_Dx_7GXbP9U7A0AadASAdYUCZk_TVLM0w-xyySOJbFq++w@mail.gmail.com>

Hi blog creation people,

I was going to submit blog.pytest.org to planet.python.org, however
one of the checks they do is validation and it seems our blog fails to
validate:

https://validator.w3.org/feed/check.cgi?url=http://blog.pytest.org/feeds/all.rss.xml

If anyone knows how to fix these please go ahead.  It'll probably take
quite a while before I would get round to fixing these.  But let me
know once it passes so I can submit it to planet.python.org!


Thanks,
Floris

From me at the-compiler.org  Mon Jul  4 07:58:21 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 4 Jul 2016 13:58:21 +0200
Subject: [pytest-dev] Blog RSS invalid
In-Reply-To: <CAAWk_Dx_7GXbP9U7A0AadASAdYUCZk_TVLM0w-xyySOJbFq++w@mail.gmail.com>
References: <CAAWk_Dx_7GXbP9U7A0AadASAdYUCZk_TVLM0w-xyySOJbFq++w@mail.gmail.com>
Message-ID: <20160704115821.2ztjasyzbkz5gfvs@tonks>

* Floris Bruynooghe <flub at devork.be> [2016-07-04 12:56:25 +0100]:
> Hi blog creation people,
> 
> I was going to submit blog.pytest.org to planet.python.org, however
> one of the checks they do is validation and it seems our blog fails to
> validate:
> 
> https://validator.w3.org/feed/check.cgi?url=http://blog.pytest.org/feeds/all.rss.xml
> 
> If anyone knows how to fix these please go ahead.  It'll probably take
> quite a while before I would get round to fixing these.  But let me
> know once it passes so I can submit it to planet.python.org!

There's an issue for it FWIW:
https://github.com/pytest-dev/blog.pytest.org/issues/9

No idea off-hand I'm afraid.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160704/84dc570d/attachment.sig>

From nicoddemus at gmail.com  Wed Jul  6 07:08:53 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 06 Jul 2016 11:08:53 +0000
Subject: [pytest-dev] pytest.readthedocs.io pointing to "latest"
Message-ID: <CA+RQFfc+B0-i-aOACpYGex5AMzueapEmFKMb0nDBOysDcKtZ=g@mail.gmail.com>

Hi all,

I have configured http://pytest.readthedocs.io/ to point to ?latest? by
default (which represents master branch) rather than ?stable? (which
represents ?latest release/tag?). I think it makes more sense because
usually our changes to the documentation in master don?t change behavior,
but are fixes to the ?live? documentation like typos, removing the sprint
banner, fixing dead links, etc, so makes sense for it to be up-to-date at
all times. The only ?downside? is that 2.9.3.dev shows up in the CHANGELOG,
but I don?t see that as a bad thing, because it is clear that it is the
not-released, development version, and one can argue that it is even nice
because shows up what?s coming in the next release.

Let me know if any of you disagrees or have any other comments.

Holger,

Any chance of pointing docs.pytest.org to http://pytest.readthedocs.io/ in
your server before 3.0? I really would like to have that ready, if
possible. :)

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

From oliver at bestwalter.de  Wed Jul  6 07:16:12 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Wed, 06 Jul 2016 11:16:12 +0000
Subject: [pytest-dev] pytest.readthedocs.io pointing to "latest"
In-Reply-To: <CA+RQFfc+B0-i-aOACpYGex5AMzueapEmFKMb0nDBOysDcKtZ=g@mail.gmail.com>
References: <CA+RQFfc+B0-i-aOACpYGex5AMzueapEmFKMb0nDBOysDcKtZ=g@mail.gmail.com>
Message-ID: <CAG5CgtrEMywEH19QMBJKvN4JJ=xnT2DDzVs8tGRM4Nk=JFbm4g@mail.gmail.com>

+1 :)

On Wed, 6 Jul 2016 at 13:09 Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi all,
>
> I have configured http://pytest.readthedocs.io/ to point to ?latest? by
> default (which represents master branch) rather than ?stable? (which
> represents ?latest release/tag?). I think it makes more sense because
> usually our changes to the documentation in master don?t change behavior,
> but are fixes to the ?live? documentation like typos, removing the sprint
> banner, fixing dead links, etc, so makes sense for it to be up-to-date at
> all times. The only ?downside? is that 2.9.3.dev shows up in the CHANGELOG,
> but I don?t see that as a bad thing, because it is clear that it is the
> not-released, development version, and one can argue that it is even nice
> because shows up what?s coming in the next release.
>
> Let me know if any of you disagrees or have any other comments.
>
> Holger,
>
> Any chance of pointing docs.pytest.org to http://pytest.readthedocs.io/
> in your server before 3.0? I really would like to have that ready, if
> possible. :)
>
> Cheers,
> Bruno.
> ?
> _______________________________________________
> 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/20160706/16a9fee0/attachment.html>

From florian.schulze at gmx.net  Thu Jul  7 07:14:27 2016
From: florian.schulze at gmx.net (Florian Schulze)
Date: Thu, 07 Jul 2016 13:14:27 +0200
Subject: [pytest-dev] Info on move from bitbucket to github
Message-ID: <5D34B278-ECAE-4038-8D07-05B81FD031E3@gmx.net>

Hi!

Who did the move from bitbucket to github? Is there a writeup, scripts, 
links to resources or anything which describes the process? The Whoosh 
package wants to make the move and needs help. So I thought I ask here 
and try to help with the move. I remember that moving the issues had 
some drawbacks for example.

Regards,
Florian Schulze

From nicoddemus at gmail.com  Thu Jul  7 07:50:57 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 07 Jul 2016 11:50:57 +0000
Subject: [pytest-dev] Info on move from bitbucket to github
In-Reply-To: <5D34B278-ECAE-4038-8D07-05B81FD031E3@gmx.net>
References: <5D34B278-ECAE-4038-8D07-05B81FD031E3@gmx.net>
Message-ID: <CA+RQFfdA0-8Ehpx3ApveFPkNEvzFSksm8ASQTPV=O+sDvqwn_w@mail.gmail.com>

Hi Florian,

 I have used this fork to move the issues for pytest:

https://github.com/nicoddemus/bitbucket_issue_migration

It can be used as a starting point. There's no how-to specifically (sorry),
but one piece of advice is: create a dummy GitHub repository to move the
issues and see how the process goes, because sometimes the script might bug
out in a particular issue or need adjustments. In that case delete the
repository and repeat the process. Once you are satisfied with the results,
you should then do the final move to the final repository. That is because
once an issue is created, it gets assigned a new id which can never be
reused again, and you want to keep the same issue id between BitBucket and
GitHub.

I remember Ronny saying he had or was working on a more robust solution, he
can supply more info.

Hope that helps,
Bruno.

On Thu, Jul 7, 2016 at 8:14 AM Florian Schulze <florian.schulze at gmx.net>
wrote:

> Hi!
>
> Who did the move from bitbucket to github? Is there a writeup, scripts,
> links to resources or anything which describes the process? The Whoosh
> package wants to make the move and needs help. So I thought I ask here
> and try to help with the move. I remember that moving the issues had
> some drawbacks for example.
>
> Regards,
> Florian Schulze
> _______________________________________________
> 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/20160707/db701dec/attachment.html>

From brianna.laugher at gmail.com  Thu Jul  7 07:52:05 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Thu, 7 Jul 2016 21:52:05 +1000
Subject: [pytest-dev] Info on move from bitbucket to github
In-Reply-To: <5D34B278-ECAE-4038-8D07-05B81FD031E3@gmx.net>
References: <5D34B278-ECAE-4038-8D07-05B81FD031E3@gmx.net>
Message-ID: <CAPjwCjvyobdNghMn4iCDV8e9jjduEpZUOBV2YxXDugL1UOfTZA@mail.gmail.com>

(also this would make a good blog post!)

On 7 July 2016 at 21:14, Florian Schulze <florian.schulze at gmx.net> wrote:

> Hi!
>
> Who did the move from bitbucket to github? Is there a writeup, scripts,
> links to resources or anything which describes the process? The Whoosh
> package wants to make the move and needs help. So I thought I ask here and
> try to help with the move. I remember that moving the issues had some
> drawbacks for example.
>
> Regards,
> Florian Schulze
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
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/20160707/0457d11f/attachment.html>

From opensource at ronnypfannschmidt.de  Thu Jul  7 17:27:11 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Thu, 7 Jul 2016 23:27:11 +0200
Subject: [pytest-dev] call for crowd-help with enabling the accurate import
 of tox issues to github
Message-ID: <b85937a1-6bda-4c4a-e6c4-1e818baf512a@ronnypfannschmidt.de>

Hi everyone,

we want to move tox to github before the next release.

however unlike the move of pytest (where we had issues with the mapping
of bitbucket usernames to git usernames )
we'd like to get started on that with a more accurate usermap

for that purpose i prototyped a small tool to deal with usermaps and
apply them to issues
however now that it mostly works, the crowd-sourceable problem is apparent,

there are dozens and dozens of usernames to verify and mark as correct,
renamed or missing

i hope for some volunteers to help me over the weekend/some free time to
run trough those in some coordination to get a reasonable amount of
those marked

my current process for the usermap is in
https://github.com/RonnyPfannschmidt/bitbucket_issue_migration/tree/master/projects-tests/tox
and currently many of those are null instead of True or matching, False
for missing or a string for telling the new name.

my hope is that sunday evening i can present a import that is reasonably
complete and acceptable as something we can move to the tox-dev org i
created on github

afterwards we will just pull the history into the repo and rejoice

Regards, Ronny


From holger at merlinux.eu  Fri Jul  8 03:38:23 2016
From: holger at merlinux.eu (holger krekel)
Date: Fri, 8 Jul 2016 09:38:23 +0200
Subject: [pytest-dev] pytest.readthedocs.io pointing to "latest"
In-Reply-To: <CA+RQFfc+B0-i-aOACpYGex5AMzueapEmFKMb0nDBOysDcKtZ=g@mail.gmail.com>
References: <CA+RQFfc+B0-i-aOACpYGex5AMzueapEmFKMb0nDBOysDcKtZ=g@mail.gmail.com>
Message-ID: <20160708073823.GH1801@uwanda>

On Wed, Jul 06, 2016 at 11:08 +0000, Bruno Oliveira wrote:
> Hi all,
> 
> I have configured http://pytest.readthedocs.io/ to point to ?latest? by
> default (which represents master branch) rather than ?stable? (which
> represents ?latest release/tag?). I think it makes more sense because
> usually our changes to the documentation in master don?t change behavior,
> but are fixes to the ?live? documentation like typos, removing the sprint
> banner, fixing dead links, etc, so makes sense for it to be up-to-date at
> all times. The only ?downside? is that 2.9.3.dev shows up in the CHANGELOG,
> but I don?t see that as a bad thing, because it is clear that it is the
> not-released, development version, and one can argue that it is even nice
> because shows up what?s coming in the next release.

sounds good to me.

> Let me know if any of you disagrees or have any other comments.
> 
> Holger,
> 
> Any chance of pointing docs.pytest.org to http://pytest.readthedocs.io/ in
> your server before 3.0? I really would like to have that ready, if
> possible. :)

i changed the CNAME record of "doc" and "docs" to point to 
pytest.readthedocs.org.  Probably takes a while to proliferate
but should work soon.

holger



> Cheers,
> Bruno.
> ?

From nicoddemus at gmail.com  Fri Jul  8 15:09:07 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 08 Jul 2016 19:09:07 +0000
Subject: [pytest-dev] pytest.readthedocs.io pointing to "latest"
In-Reply-To: <20160708073823.GH1801@uwanda>
References: <CA+RQFfc+B0-i-aOACpYGex5AMzueapEmFKMb0nDBOysDcKtZ=g@mail.gmail.com>
 <20160708073823.GH1801@uwanda>
Message-ID: <CA+RQFfcVFfBPrzLHVtgAg2Ep+3Rcer+EqTjoB+_chsZJq-1+ag@mail.gmail.com>

On Fri, Jul 8, 2016 at 4:38 AM holger krekel <holger at merlinux.eu> wrote:

> i changed the CNAME record of "doc" and "docs" to point to
> pytest.readthedocs.org.  Probably takes a while to proliferate
> but should work soon.
>

Thanks! http://doc.pytest.org/en/latest/ is already working. :)

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

From raphael at hackebrot.de  Fri Jul  8 15:59:47 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Fri, 8 Jul 2016 20:59:47 +0100
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
Message-ID: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>

Hi pytest-friends,

as we are getting closer to EuroPython and my talk on Pytest 3.0, I would be delighted if you could send me your ideas on what you feel is most important to cover. I will be spending the weekend to work on my talk and send around what I have early next week.

https://ep2016.europython.eu/conference/talks/pytest-30 <https://ep2016.europython.eu/conference/talks/pytest-30>

Holger sent around a list of features/improvement that we hope to ship with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4 release plans? from 25 June. What?s the current status and what do you think will be merged in the next couple of days to be included in the release?

Any feedback or questions, please let me know.

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

From nicoddemus at gmail.com  Fri Jul  8 16:50:43 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 08 Jul 2016 20:50:43 +0000
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
Message-ID: <CA+RQFfeDiz4ir67BUNNJ2CS89k3-u3RyhzVpyMoWT=xaG1+fNA@mail.gmail.com>

Hi all,

As a reminder, Oliver has compiled the list Holger sent into a page on the
Wiki: https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist, (just
updated it).

For my part, I've mostly finished the implementation of invocation-scoped
fixtures, although I need to add more tests. I plan to open a PR early next
week. I also plan to work on adding deprecation warnings to "yield tests"
and pytest_funcarg fixtures.

As for "removing assert reinterpret", it is almost ready AFAIK.

Here's what's left, which would be nice to have in 3.0:

* deprecation docs
* docs restructuring

Cheers,
Bruno.


On Fri, Jul 8, 2016 at 5:05 PM Raphael Pierzina <raphael at hackebrot.de>
wrote:

> Hi pytest-friends,
>
> as we are getting closer to EuroPython and my talk on Pytest 3.0, I would
> be delighted if you could send me your ideas on what you feel is most
> important to cover. I will be spending the weekend to work on my talk and
> send around what I have early next week.
>
> https://ep2016.europython.eu/conference/talks/pytest-30
>
> Holger sent around a list of features/improvement that we hope to ship
> with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4
> release plans? from 25 June. What?s the current status and what do you
> think will be merged in the next couple of days to be included in the
> release?
>
> Any feedback or questions, please let me know.
>
> Cheers
> Raphael
> _______________________________________________
> 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/20160708/32cd75d1/attachment.html>

From dhunt at mozilla.com  Fri Jul  8 17:20:35 2016
From: dhunt at mozilla.com (Dave Hunt)
Date: Fri, 8 Jul 2016 22:20:35 +0100
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
Message-ID: <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>

"You can now run pytest without using py dot test" then drop the mic and walk off to rapturous applause. ? #dropthedot

Dave Hunt

> On 8 Jul 2016, at 20:59, Raphael Pierzina <raphael at hackebrot.de> wrote:
> 
> Hi pytest-friends,
> 
> as we are getting closer to EuroPython and my talk on Pytest 3.0, I would be delighted if you could send me your ideas on what you feel is most important to cover. I will be spending the weekend to work on my talk and send around what I have early next week.
> 
> https://ep2016.europython.eu/conference/talks/pytest-30
> 
> Holger sent around a list of features/improvement that we hope to ship with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4 release plans? from 25 June. What?s the current status and what do you think will be merged in the next couple of days to be included in the release?
> 
> Any feedback or questions, please let me know.
> 
> Cheers
> Raphael
> _______________________________________________
> 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/20160708/9a84a524/attachment-0001.html>

From nicoddemus at gmail.com  Fri Jul  8 17:26:39 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 08 Jul 2016 21:26:39 +0000
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
 <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>
Message-ID: <CA+RQFfdkG-MHrnOiSu8rK7HnS7S37LmCc8NpqO1A98dPZG4YqQ@mail.gmail.com>

Hahaha I laughed over here!

On Fri, Jul 8, 2016 at 6:20 PM Dave Hunt <dhunt at mozilla.com> wrote:

> "You can now run pytest without using py dot test" then drop the mic and
> walk off to rapturous applause. ? #dropthedot
>
>
> Dave Hunt
>
> On 8 Jul 2016, at 20:59, Raphael Pierzina <raphael at hackebrot.de> wrote:
>
> Hi pytest-friends,
>
> as we are getting closer to EuroPython and my talk on Pytest 3.0, I would
> be delighted if you could send me your ideas on what you feel is most
> important to cover. I will be spending the weekend to work on my talk and
> send around what I have early next week.
>
> https://ep2016.europython.eu/conference/talks/pytest-30
>
> Holger sent around a list of features/improvement that we hope to ship
> with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4
> release plans? from 25 June. What?s the current status and what do you
> think will be merged in the next couple of days to be included in the
> release?
>
> Any feedback or questions, please let me know.
>
> Cheers
> Raphael
>
> _______________________________________________
> 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/20160708/dded8b17/attachment.html>

From omarkohl at gmail.com  Fri Jul  8 18:01:06 2016
From: omarkohl at gmail.com (Omar Kohl)
Date: Sat, 9 Jul 2016 00:01:06 +0200
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
 <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>
Message-ID: <578022A2.9080508@gmail.com>

+1 :-D

On 08.07.2016 23:20, Dave Hunt wrote:
> "You can now run pytest without using py dot test" then drop the mic
> and walk off to rapturous applause. ? #dropthedot
>
> Dave Hunt
>
> On 8 Jul 2016, at 20:59, Raphael Pierzina <raphael at hackebrot.de
> <mailto:raphael at hackebrot.de>> wrote:
>
>> Hi pytest-friends,
>>
>> as we are getting closer to EuroPython and my talk on Pytest 3.0, I
>> would be delighted if you could send me your ideas on what you feel
>> is most important to cover. I will be spending the weekend to work on
>> my talk and send around what I have early next week.
>>
>> https://ep2016.europython.eu/conference/talks/pytest-30
>>
>> Holger sent around a list of features/improvement that we hope to
>> ship with pytest (and tox); search for ?[pytest-dev] pytest-3.0 /
>> tox-2.4 release plans? from 25 June. What?s the current status and
>> what do you think will be merged in the next couple of days to be
>> included in the release?
>>
>> Any feedback or questions, please let me know.
>>
>> Cheers
>> Raphael
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org <mailto: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


-- 
Omar Kohl

***************************************************************
Emails are not secure! They can be read and even modified by a 
third party.
http://en.wikipedia.org/wiki/Email#Privacy_concerns

Use OpenPGP for secure encryption: Thunderbird & Enigmail are 
free and easy to configure. For Windows users: Gpg4win.

My PGP fingerprint:
B6DC 00BC D4EB 67DD 121B  393C 6CC2 6B44 1B05 A275
***************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160709/31264de9/attachment.html>

From raphael at hackebrot.de  Fri Jul  8 18:18:45 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Fri, 8 Jul 2016 23:18:45 +0100
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
 <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>
Message-ID: <C35BDF5A-156F-43B8-B4C8-49A28C41EAE2@hackebrot.de>

If only Floris wouldn?t be around :D I reckon he?s not going to approve of this and might throw rotten tomatoes at me. #DoNotWant


> On 08 Jul 2016, at 22:20, Dave Hunt <dhunt at mozilla.com> wrote:
> 
> "You can now run pytest without using py dot test" then drop the mic and walk off to rapturous applause. ? #dropthedot
> 
> Dave Hunt
> 
> On 8 Jul 2016, at 20:59, Raphael Pierzina <raphael at hackebrot.de <mailto:raphael at hackebrot.de>> wrote:
> 
>> Hi pytest-friends,
>> 
>> as we are getting closer to EuroPython and my talk on Pytest 3.0, I would be delighted if you could send me your ideas on what you feel is most important to cover. I will be spending the weekend to work on my talk and send around what I have early next week.
>> 
>> https://ep2016.europython.eu/conference/talks/pytest-30 <https://ep2016.europython.eu/conference/talks/pytest-30>
>> 
>> Holger sent around a list of features/improvement that we hope to ship with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4 release plans? from 25 June. What?s the current status and what do you think will be merged in the next couple of days to be included in the release?
>> 
>> Any feedback or questions, please let me know.
>> 
>> Cheers
>> Raphael
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org <mailto:pytest-dev at python.org>
>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160708/6d84985b/attachment-0001.html>

From flub at devork.be  Fri Jul  8 19:52:16 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Sat, 9 Jul 2016 00:52:16 +0100
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <C35BDF5A-156F-43B8-B4C8-49A28C41EAE2@hackebrot.de>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
 <3A1C0C63-0D19-4ADC-B6F8-9732A3600E53@mozilla.com>
 <C35BDF5A-156F-43B8-B4C8-49A28C41EAE2@hackebrot.de>
Message-ID: <CAAWk_DzToG37wYSvDJMgXNO5oo5QPNCHZEhZ0UcOSj-ZDmfRmA@mail.gmail.com>

I'll just sneak in a slide when you leave your laptop unattended...
On 8 Jul 2016 23:19, "Raphael Pierzina" <raphael at hackebrot.de> wrote:

> If only Floris wouldn?t be around :D I reckon he?s not going to approve of
> this and might throw rotten tomatoes at me. #DoNotWant
>
>
> On 08 Jul 2016, at 22:20, Dave Hunt <dhunt at mozilla.com> wrote:
>
> "You can now run pytest without using py dot test" then drop the mic and
> walk off to rapturous applause. ? #dropthedot
>
> Dave Hunt
>
> On 8 Jul 2016, at 20:59, Raphael Pierzina <raphael at hackebrot.de> wrote:
>
> Hi pytest-friends,
>
> as we are getting closer to EuroPython and my talk on Pytest 3.0, I would
> be delighted if you could send me your ideas on what you feel is most
> important to cover. I will be spending the weekend to work on my talk and
> send around what I have early next week.
>
> https://ep2016.europython.eu/conference/talks/pytest-30
>
> Holger sent around a list of features/improvement that we hope to ship
> with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4
> release plans? from 25 June. What?s the current status and what do you
> think will be merged in the next couple of days to be included in the
> release?
>
> Any feedback or questions, please let me know.
>
> Cheers
> Raphael
>
> _______________________________________________
> 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/20160709/0e90630b/attachment.html>

From mail at florian-schulze.net  Sat Jul  9 05:25:41 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Sat, 09 Jul 2016 11:25:41 +0200
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
Message-ID: <85A3678C-A51C-45F6-A45F-1754AB83C785@florian-schulze.net>

During one of the discussions I agreed to work on a small bit. Problem 
is, I didn't make a note and can't remember and I'm not on the list in 
the wiki 
(https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist). Does 
anyone remember?

Regards,
Florian Schulze


On 8 Jul 2016, at 21:59, Raphael Pierzina wrote:

> Hi pytest-friends,
>
> as we are getting closer to EuroPython and my talk on Pytest 3.0, I 
> would be delighted if you could send me your ideas on what you feel is 
> most important to cover. I will be spending the weekend to work on my 
> talk and send around what I have early next week.
>
> https://ep2016.europython.eu/conference/talks/pytest-30 
> <https://ep2016.europython.eu/conference/talks/pytest-30>
>
> Holger sent around a list of features/improvement that we hope to ship 
> with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4 
> release plans? from 25 June. What?s the current status and what do 
> you think will be merged in the next couple of days to be included in 
> the release?
>
> Any feedback or questions, please let me know.
>
> Cheers
> Raphael_______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From mail at florian-schulze.net  Sat Jul  9 07:02:58 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Sat, 09 Jul 2016 13:02:58 +0200
Subject: [pytest-dev] Announcing pytest-pdb
Message-ID: <6D91C0D2-CFD0-40A9-BE5D-A6EBC3052AA2@florian-schulze.net>

Hi!

I just released https://pypi.python.org/pypi/pytest-pdb

It adds a ``whichtest`` command to pdb. It prints identifying 
information about the current test you are in. Much easier than looking 
through the stack trace of ``which`` and it prints info on parameters.

Regards,
Florian Schulze

From oliver at bestwalter.de  Mon Jul 11 08:48:49 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Mon, 11 Jul 2016 12:48:49 +0000
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <85A3678C-A51C-45F6-A45F-1754AB83C785@florian-schulze.net>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
 <85A3678C-A51C-45F6-A45F-1754AB83C785@florian-schulze.net>
Message-ID: <CAG5CgtpgnW1Js55F2QP+NvaG=DOEyaCjdnm6Uk+HtjYLBQ0GSA@mail.gmail.com>

Hi,

let's keep the #dropthedot in mind for the release that's really funny :D

@Florian - sorry I can't remember something specific. I compiled the
release list from the etherpad (https://pad.riseup.net/p/6pMxJxjNeFEL) - I
hope I didn't overlook anything - maybe have a quick look if I just didn't
process something correctly. The only other thing I remember is that we
discussed about the warnings and thought about integrating pytest-warnings
into core to have better filtering options - only we didn't think it's
realistic for 3.0 so this won't be it I guess, but maybe it triggers your
memory.

About my bit on the list: I hope to compile the deprecations docs today and
send a PR so that there is some time left to review them. @Brianna - I am
not quite sure where I should place the docs as the restructuring is in
process as well. Can you give me a quick hint? Oterrwise I'll just do the
PR against features branch in the unrestructured docs first.

Cheers
Oliver

On Sat, 9 Jul 2016 at 11:25 Florian Schulze <mail at florian-schulze.net>
wrote:

> During one of the discussions I agreed to work on a small bit. Problem
> is, I didn't make a note and can't remember and I'm not on the list in
> the wiki
> (https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist). Does
> anyone remember?
>
> Regards,
> Florian Schulze
>
>
> On 8 Jul 2016, at 21:59, Raphael Pierzina wrote:
>
> > Hi pytest-friends,
> >
> > as we are getting closer to EuroPython and my talk on Pytest 3.0, I
> > would be delighted if you could send me your ideas on what you feel is
> > most important to cover. I will be spending the weekend to work on my
> > talk and send around what I have early next week.
> >
> > https://ep2016.europython.eu/conference/talks/pytest-30
> > <https://ep2016.europython.eu/conference/talks/pytest-30>
> >
> > Holger sent around a list of features/improvement that we hope to ship
> > with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4
> > release plans? from 25 June. What?s the current status and what do
> > you think will be merged in the next couple of days to be included in
> > the release?
> >
> > Any feedback or questions, please let me know.
> >
> > Cheers
> > Raphael_______________________________________________
> > 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/20160711/97d5e8cf/attachment.html>

From oliver at bestwalter.de  Mon Jul 11 11:53:09 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Mon, 11 Jul 2016 15:53:09 +0000
Subject: [pytest-dev] RFC deprecation policy
Message-ID: <CAG5CgtoHZGYsEJ5o8wEVj3E40Sm98hWVihWk5qe5geOA3-AC4Q@mail.gmail.com>

Hi all,

while it's still in the air where I shall place the precious text I thusly
have constructed, I would like to give you the chance to comment on it,
especially is something is still missing. I tried to keep it as sweet as
simple as I could - maybe we should add the command line parameter to shut
the warnings up right in there as well (add hint about
``--disable-pytest-warnings``)?

Here's the gist:
https://gist.github.com/obestwalter/60080d472dc5c0a97ddc265e985f1aae

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

From nicoddemus at gmail.com  Mon Jul 11 13:55:44 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 11 Jul 2016 17:55:44 +0000
Subject: [pytest-dev] RFC deprecation policy
In-Reply-To: <CAG5CgtoHZGYsEJ5o8wEVj3E40Sm98hWVihWk5qe5geOA3-AC4Q@mail.gmail.com>
References: <CAG5CgtoHZGYsEJ5o8wEVj3E40Sm98hWVihWk5qe5geOA3-AC4Q@mail.gmail.com>
Message-ID: <CA+RQFfcbQdCmQuoxK=82D4kfAugjK0q+Bh290ZbJq895CT6e_w@mail.gmail.com>

Hi Oliver,

Excellent work! I made a small comment on the gist itself. :)

Cheers,
Bruno.

On Mon, Jul 11, 2016 at 2:50 PM Oliver Bestwalter <oliver at bestwalter.de>
wrote:

> Hi all,
>
> while it's still in the air where I shall place the precious text I thusly
> have constructed, I would like to give you the chance to comment on it,
> especially is something is still missing. I tried to keep it as sweet as
> simple as I could - maybe we should add the command line parameter to shut
> the warnings up right in there as well (add hint about
> ``--disable-pytest-warnings``)?
>
> Here's the gist:
> https://gist.github.com/obestwalter/60080d472dc5c0a97ddc265e985f1aae
>
> Cheers
> Oliver
> _______________________________________________
> 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/20160711/f243d6aa/attachment.html>

From genml+pytest-dev at thequod.de  Mon Jul 11 16:58:23 2016
From: genml+pytest-dev at thequod.de (Daniel Hahler)
Date: Mon, 11 Jul 2016 22:58:23 +0200
Subject: [pytest-dev] RFC deprecation policy
In-Reply-To: <CAG5CgtoHZGYsEJ5o8wEVj3E40Sm98hWVihWk5qe5geOA3-AC4Q@mail.gmail.com>
References: <CAG5CgtoHZGYsEJ5o8wEVj3E40Sm98hWVihWk5qe5geOA3-AC4Q@mail.gmail.com>
Message-ID: <a7518b46-b250-56a4-3c59-5eb7b13829fb@thequod.de>

On 11.07.2016 17:53, Oliver Bestwalter wrote:

> Here's the gist: https://gist.github.com/obestwalter/60080d472dc5c0a97ddc265e985f1aae

Awesome, thanks!

I've forked and updated it at https://gist.github.com/blueyed/c7a55ae39b29247bce137d1e3c4288fb, but mostly deleted things that seemed to be implicit.
https://gist.github.com/blueyed/c7a55ae39b29247bce137d1e3c4288fb/revisions


Cheers,
Daniel.

From genml+pytest-dev at thequod.de  Mon Jul 11 17:16:36 2016
From: genml+pytest-dev at thequod.de (Daniel Hahler)
Date: Mon, 11 Jul 2016 23:16:36 +0200
Subject: [pytest-dev] Announcing pytest-pdb
In-Reply-To: <6D91C0D2-CFD0-40A9-BE5D-A6EBC3052AA2@florian-schulze.net>
References: <6D91C0D2-CFD0-40A9-BE5D-A6EBC3052AA2@florian-schulze.net>
Message-ID: <a84ca425-0456-c926-d073-026f10c0a801@thequod.de>

On 09.07.2016 13:02, Florian Schulze wrote:

> I just released https://pypi.python.org/pypi/pytest-pdb

> It adds a ``whichtest`` command to pdb. It prints identifying information about the current test you are in. Much easier than looking through the stack trace of ``which`` and it prints info on parameters.

Very nice!

Just tried it and it works as advertised.  Looking forward to more awesomeness in this regard!

But pdbpp does not autocomplete the "whichtest" command, can this be done?


Cheers,
Daniel.

From genml+pytest-dev at thequod.de  Mon Jul 11 17:26:05 2016
From: genml+pytest-dev at thequod.de (Daniel Hahler)
Date: Mon, 11 Jul 2016 23:26:05 +0200
Subject: [pytest-dev] pytest 3.0 release check list
In-Reply-To: <CAG5CgtqN7o8ehe1zZdWyfNSHzS7oRG=-q0ZCPfu0cQpgaMCK6g@mail.gmail.com>
References: <CAG5CgtqN7o8ehe1zZdWyfNSHzS7oRG=-q0ZCPfu0cQpgaMCK6g@mail.gmail.com>
Message-ID: <4a4274fc-dffd-4f65-0162-c0d004ca7939@thequod.de>

On 29.06.2016 19:16, Oliver Bestwalter wrote:

> I created a wiki page containing the checklist for the 3.0 release that resulted from our discussion during the sprint.
> 
> https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist

I've added a link for issues/PRs tagged for the 3.0 milestone.
There are 42 currently: https://github.com/pytest-dev/pytest/milestone/2


Cheers,
Daniel.

From oliver at bestwalter.de  Mon Jul 11 17:56:36 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Mon, 11 Jul 2016 21:56:36 +0000
Subject: [pytest-dev] RFC deprecation policy
In-Reply-To: <a7518b46-b250-56a4-3c59-5eb7b13829fb@thequod.de>
References: <CAG5CgtoHZGYsEJ5o8wEVj3E40Sm98hWVihWk5qe5geOA3-AC4Q@mail.gmail.com>
 <a7518b46-b250-56a4-3c59-5eb7b13829fb@thequod.de>
Message-ID: <CAG5CgtogwJSNFkFeumOpCKsp-urnjwYso45F+=yf16A2wh6KUg@mail.gmail.com>

Hi Bruno and Daniel,

thanks for reviewing.

@Bruno will add the silence option also then like suggested

@Daniel: yeah I actually stumbled over that sentence while reading through
it again a bit later. Really not necessary. Even shorter - nice :)

Cheers
Oliver

On Mon, 11 Jul 2016 at 22:58 Daniel Hahler <genml+pytest-dev at thequod.de>
wrote:

> On 11.07.2016 17:53, Oliver Bestwalter wrote:
>
> > Here's the gist:
> https://gist.github.com/obestwalter/60080d472dc5c0a97ddc265e985f1aae
>
> Awesome, thanks!
>
> I've forked and updated it at
> https://gist.github.com/blueyed/c7a55ae39b29247bce137d1e3c4288fb, but
> mostly deleted things that seemed to be implicit.
> https://gist.github.com/blueyed/c7a55ae39b29247bce137d1e3c4288fb/revisions
>
>
> Cheers,
> Daniel.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160711/4ab09631/attachment.html>

From mail at florian-schulze.net  Tue Jul 12 02:28:55 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Tue, 12 Jul 2016 08:28:55 +0200
Subject: [pytest-dev] Announcing pytest-pdb
In-Reply-To: <a84ca425-0456-c926-d073-026f10c0a801@thequod.de>
References: <6D91C0D2-CFD0-40A9-BE5D-A6EBC3052AA2@florian-schulze.net>
 <a84ca425-0456-c926-d073-026f10c0a801@thequod.de>
Message-ID: <ADA0D512-0D93-4037-9EAC-3EB119F823F4@florian-schulze.net>

On 11 Jul 2016, at 23:16, Daniel Hahler wrote:
> On 09.07.2016 13:02, Florian Schulze wrote:
>
>> I just released https://pypi.python.org/pypi/pytest-pdb
>
>> It adds a ``whichtest`` command to pdb. It prints identifying 
>> information about the current test you are in. Much easier than 
>> looking through the stack trace of ``which`` and it prints info on 
>> parameters.
>
> Very nice!
>
> Just tried it and it works as advertised.  Looking forward to more 
> awesomeness in this regard!
>
> But pdbpp does not autocomplete the "whichtest" command, can this be 
> done?

Not sure. The issue is, that I inject methods into the pdb.Pdb class and 
the autocomplete setup is done before. Maybe if we do the patching on 
module import it will be early enough. Otherwise we might have to add 
specific code to update autocomplete, but then we might have to support 
all kinds of pdb addons.

Regards,
Florian Schulze

From nicoddemus at gmail.com  Thu Jul 14 16:21:18 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 14 Jul 2016 20:21:18 +0000
Subject: [pytest-dev] Postpone 3.0?
Message-ID: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>

Hi pytesters,

Our original target date for pytest 3.0 was around this week (just before
EuroPython), but it seems we are not going to make it as there are some
issues still in the 3.0 check list which have not been merged:

https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist

My question is if we should delay the release a little bit and give more
time to people to work on them for 3.0, or bite the bullet and make the
release anyway this weekend/early next week? And if we decide to delay,
what people think would be a good time for a new target date?

Personally I would rather wait a little more because I consider the
remaining issues important to go in 3.0.

Btw, I was taking a look at the Pulse page on GitHub (
https://github.com/pytest-dev/pytest/pulse
<https://github.com/pytest-dev/pytest/pulse/monthly>) and in the last 7
days we have merged 16 PRs. That's awesome. :)

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

From raphael at hackebrot.de  Thu Jul 14 18:20:51 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Thu, 14 Jul 2016 23:20:51 +0100
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
Message-ID: <39A60272-F6DB-4B0A-B115-805F5B184D08@hackebrot.de>

Hi Bruno,

I?m happy with either, but I need to know as soon as possible as it?s only a week until my EuroPython talk.

Right now, I find it quite hard to work on my slides w/o knowing when pytest 3.0 is going to land and what it will include.

Please don?t get me wrong. Again, anything works for me as long as I know a preliminary release date and scope as I want to prepare demos for the presentation.

Cheers
Raphael

> On 14 Jul 2016, at 21:21, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Hi pytesters,
> 
> Our original target date for pytest 3.0 was around this week (just before EuroPython), but it seems we are not going to make it as there are some issues still in the 3.0 check list which have not been merged:
> 
> https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist <https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist>
> 
> My question is if we should delay the release a little bit and give more time to people to work on them for 3.0, or bite the bullet and make the release anyway this weekend/early next week? And if we decide to delay, what people think would be a good time for a new target date?
> 
> Personally I would rather wait a little more because I consider the remaining issues important to go in 3.0.
> 
> Btw, I was taking a look at the Pulse page on GitHub (https://github.com/pytest-dev/pytest/pulse <https://github.com/pytest-dev/pytest/pulse/monthly>) and in the last 7 days we have merged 16 PRs. That's awesome. :)
> 
> Cheers,
> Bruno.
> 
> 
> _______________________________________________
> 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/20160714/1dae0c7c/attachment.html>

From brianna.laugher at gmail.com  Thu Jul 14 18:45:27 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Fri, 15 Jul 2016 08:45:27 +1000
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
Message-ID: <CAPjwCjs2oHPZUxQ_JikB267SV=0J5TOOSaV8nMjyPSk63+GWYA@mail.gmail.com>

It's mainly Floris, Oliver and me that are the hold up right? Removing
reinterpret assert and 2x docs.
I hope to work on the docs restructure this weekend and at a minimum make
it clear what tasks are left so it's easier for other people to help.

Brianna

On 15/07/2016 6:21 AM, "Bruno Oliveira" <nicoddemus at gmail.com> wrote:

> Hi pytesters,
>
> Our original target date for pytest 3.0 was around this week (just before
> EuroPython), but it seems we are not going to make it as there are some
> issues still in the 3.0 check list which have not been merged:
>
> https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist
>
> My question is if we should delay the release a little bit and give more
> time to people to work on them for 3.0, or bite the bullet and make the
> release anyway this weekend/early next week? And if we decide to delay,
> what people think would be a good time for a new target date?
>
> Personally I would rather wait a little more because I consider the
> remaining issues important to go in 3.0.
>
> Btw, I was taking a look at the Pulse page on GitHub (
> https://github.com/pytest-dev/pytest/pulse
> <https://github.com/pytest-dev/pytest/pulse/monthly>) and in the last 7
> days we have merged 16 PRs. That's awesome. :)
>
> Cheers,
> Bruno.
>
>
>
> _______________________________________________
> 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/20160715/5e71e2ec/attachment.html>

From nicoddemus at gmail.com  Thu Jul 14 18:46:31 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 14 Jul 2016 22:46:31 +0000
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <39A60272-F6DB-4B0A-B115-805F5B184D08@hackebrot.de>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <39A60272-F6DB-4B0A-B115-805F5B184D08@hackebrot.de>
Message-ID: <CA+RQFfdiY_bGc_wq9zDqHxVqYB_Lmfhfu-SrvnixipKAzPiTpQ@mail.gmail.com>

Hi Raphael,

On Thu, Jul 14, 2016 at 7:20 PM Raphael Pierzina <raphael at hackebrot.de>
wrote:

> Hi Bruno,
>
> I?m happy with either, but I need to know as soon as possible as it?s only
> a week until my EuroPython talk.
>
> Right now, I find it quite hard to work on my slides w/o knowing when
> pytest 3.0 is going to land and what it will include.
>

Sure thing!

I have a draft of a "What's new in Pytest 3.0" post for the blog which I
will open a PR for shortly; I'm sure you can use that as a basis of what's
going into the version.

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

From raphael at hackebrot.de  Thu Jul 14 18:52:31 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Thu, 14 Jul 2016 23:52:31 +0100
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <CA+RQFfdiY_bGc_wq9zDqHxVqYB_Lmfhfu-SrvnixipKAzPiTpQ@mail.gmail.com>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <39A60272-F6DB-4B0A-B115-805F5B184D08@hackebrot.de>
 <CA+RQFfdiY_bGc_wq9zDqHxVqYB_Lmfhfu-SrvnixipKAzPiTpQ@mail.gmail.com>
Message-ID: <ADB8EA15-05E4-408F-A85B-32D66EDAFF24@hackebrot.de>

Hi Bruno,

that?d be incredibly helpful! Please feel free to email me your draft off-list even if it?s not ready for a PR.

Thank you
Raphael

> On 14 Jul 2016, at 23:46, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Hi Raphael,  
> 
> On Thu, Jul 14, 2016 at 7:20 PM Raphael Pierzina <raphael at hackebrot.de <mailto:raphael at hackebrot.de>> wrote:
> Hi Bruno,
> 
> I?m happy with either, but I need to know as soon as possible as it?s only a week until my EuroPython talk.
> 
> Right now, I find it quite hard to work on my slides w/o knowing when pytest 3.0 is going to land and what it will include.
> 
> Sure thing!
> 
> I have a draft of a "What's new in Pytest 3.0" post for the blog which I will open a PR for shortly; I'm sure you can use that as a basis of what's going into the version. 
> 
> Cheers,
> Bruno.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160714/92fc0ee5/attachment.html>

From raphael at hackebrot.de  Thu Jul 14 18:59:23 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Thu, 14 Jul 2016 23:59:23 +0100
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <CAPjwCjs2oHPZUxQ_JikB267SV=0J5TOOSaV8nMjyPSk63+GWYA@mail.gmail.com>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <CAPjwCjs2oHPZUxQ_JikB267SV=0J5TOOSaV8nMjyPSk63+GWYA@mail.gmail.com>
Message-ID: <517B8249-0BAB-4F19-9411-475E6953A6B1@hackebrot.de>

Hi Brianna,

at this point I wouldn?t worry too much about the docs as they won?t be part of the distribution.

That being said, I will however briefly cover what we?ve discussed and what is planned for new structure of the documentation.

Any input is as usual highly appreciated!

Thank you
Raphael

> On 14 Jul 2016, at 23:45, Brianna Laugher <brianna.laugher at gmail.com> wrote:
> 
> It's mainly Floris, Oliver and me that are the hold up right? Removing reinterpret assert and 2x docs.
> I hope to work on the docs restructure this weekend and at a minimum make it clear what tasks are left so it's easier for other people to help.
> 
> Brianna
> 
> 
> On 15/07/2016 6:21 AM, "Bruno Oliveira" <nicoddemus at gmail.com <mailto:nicoddemus at gmail.com>> wrote:
> Hi pytesters,
> 
> Our original target date for pytest 3.0 was around this week (just before EuroPython), but it seems we are not going to make it as there are some issues still in the 3.0 check list which have not been merged:
> 
> https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist <https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist>
> 
> My question is if we should delay the release a little bit and give more time to people to work on them for 3.0, or bite the bullet and make the release anyway this weekend/early next week? And if we decide to delay, what people think would be a good time for a new target date?
> 
> Personally I would rather wait a little more because I consider the remaining issues important to go in 3.0.
> 
> Btw, I was taking a look at the Pulse page on GitHub (https://github.com/pytest-dev/pytest/pulse <https://github.com/pytest-dev/pytest/pulse/monthly>) and in the last 7 days we have merged 16 PRs. That's awesome. :)
> 
> Cheers,
> Bruno.
> 
> 
> 
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org <mailto:pytest-dev at python.org>
> https://mail.python.org/mailman/listinfo/pytest-dev <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/20160714/eb97161e/attachment.html>

From nicoddemus at gmail.com  Thu Jul 14 19:14:44 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 14 Jul 2016 23:14:44 +0000
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <ADB8EA15-05E4-408F-A85B-32D66EDAFF24@hackebrot.de>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <39A60272-F6DB-4B0A-B115-805F5B184D08@hackebrot.de>
 <CA+RQFfdiY_bGc_wq9zDqHxVqYB_Lmfhfu-SrvnixipKAzPiTpQ@mail.gmail.com>
 <ADB8EA15-05E4-408F-A85B-32D66EDAFF24@hackebrot.de>
Message-ID: <CA+RQFfetJhKssqOBU4ZHWjOSgSvJrvawuL2=8SaL75ZbC6uWZg@mail.gmail.com>

On Thu, Jul 14, 2016 at 7:52 PM Raphael Pierzina <raphael at hackebrot.de>
wrote:

> that?d be incredibly helpful! Please feel free to email me your draft
> off-list even if it?s not ready for a PR.
>

Just pushed; it is still in draft form and this will be merged only after
pytest-3.0 is released anyway. I plan to work more on it, perhaps adding
more examples or improve the writing, but meanwhile comments and
suggestions from everyone are welcome! :)

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

From oliver at bestwalter.de  Fri Jul 15 04:32:55 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Fri, 15 Jul 2016 08:32:55 +0000
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <CA+RQFfetJhKssqOBU4ZHWjOSgSvJrvawuL2=8SaL75ZbC6uWZg@mail.gmail.com>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <39A60272-F6DB-4B0A-B115-805F5B184D08@hackebrot.de>
 <CA+RQFfdiY_bGc_wq9zDqHxVqYB_Lmfhfu-SrvnixipKAzPiTpQ@mail.gmail.com>
 <ADB8EA15-05E4-408F-A85B-32D66EDAFF24@hackebrot.de>
 <CA+RQFfetJhKssqOBU4ZHWjOSgSvJrvawuL2=8SaL75ZbC6uWZg@mail.gmail.com>
Message-ID: <CAG5CgtqQg8RE8wWM+wTp4QGvmUTEJT_tmNSiEN0uHDDeExxpOQ@mail.gmail.com>

Hi,

I will prepare a PR with the little text about deprecation at the weekend.
Although I would also love to help with the rest of the docs restructuring,
I am not sure if I can carve out some time for this.

Cheers
Oliver


On Fri, 15 Jul 2016 at 01:14 Bruno Oliveira <nicoddemus at gmail.com> wrote:

> On Thu, Jul 14, 2016 at 7:52 PM Raphael Pierzina <raphael at hackebrot.de>
> wrote:
>
>> that?d be incredibly helpful! Please feel free to email me your draft
>> off-list even if it?s not ready for a PR.
>>
>
> Just pushed; it is still in draft form and this will be merged only after
> pytest-3.0 is released anyway. I plan to work more on it, perhaps adding
> more examples or improve the writing, but meanwhile comments and
> suggestions from everyone are welcome! :)
>
> Cheers,
> Bruno.
> _______________________________________________
> 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/20160715/cb0906f2/attachment-0001.html>

From flub at devork.be  Fri Jul 15 10:29:18 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Fri, 15 Jul 2016 15:29:18 +0100
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <CAPjwCjs2oHPZUxQ_JikB267SV=0J5TOOSaV8nMjyPSk63+GWYA@mail.gmail.com>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <CAPjwCjs2oHPZUxQ_JikB267SV=0J5TOOSaV8nMjyPSk63+GWYA@mail.gmail.com>
Message-ID: <CAAWk_DxOdm9=ftBv4JVjBknBKELN8jR3UGFhrnOCu1uEXoTcTw@mail.gmail.com>

On 14 July 2016 at 23:45, Brianna Laugher <brianna.laugher at gmail.com> wrote:
> It's mainly Floris, Oliver and me that are the hold up right? Removing
> reinterpret assert and 2x docs.

Reinterpret is now removed as of this morning!  I should do one more
PR with some doc updates.  Is that fine to do against current docs in
the repo for the doc-reorg?

The milestone (https://github.com/pytest-dev/pytest/milestone/2) has a
lot of things still outstanding.  I'm happy to postpone, we could aim
for the end of the EuroPython sprints?  (although I won't be around
for that weekend)  Or maybe a week later even as sprints probably
introduce some instability.  So I'd say aim for 1st August maybe?

Speaking of the EuroPython sprints, is anybody going to be there to
organise a py.test sprint?  Raphael might still be (but then he might
want to defect to cookiecutter), Florian as well not sure about
others?  Anyone want to volunteer leading a sprint?


Floris

From me at the-compiler.org  Fri Jul 15 12:00:36 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 15 Jul 2016 18:00:36 +0200
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <CAAWk_DxOdm9=ftBv4JVjBknBKELN8jR3UGFhrnOCu1uEXoTcTw@mail.gmail.com>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <CAPjwCjs2oHPZUxQ_JikB267SV=0J5TOOSaV8nMjyPSk63+GWYA@mail.gmail.com>
 <CAAWk_DxOdm9=ftBv4JVjBknBKELN8jR3UGFhrnOCu1uEXoTcTw@mail.gmail.com>
Message-ID: <20160715160035.ibbkauceoetoogdg@tonks>

* Floris Bruynooghe <flub at devork.be> [2016-07-15 15:29:18 +0100]:
> On 14 July 2016 at 23:45, Brianna Laugher <brianna.laugher at gmail.com> wrote:
> > It's mainly Floris, Oliver and me that are the hold up right? Removing
> > reinterpret assert and 2x docs.
> 
> Reinterpret is now removed as of this morning!  I should do one more
> PR with some doc updates.  Is that fine to do against current docs in
> the repo for the doc-reorg?
> 
> The milestone (https://github.com/pytest-dev/pytest/milestone/2) has a
> lot of things still outstanding.  I'm happy to postpone, we could aim
> for the end of the EuroPython sprints?  (although I won't be around
> for that weekend)  Or maybe a week later even as sprints probably
> introduce some instability.  So I'd say aim for 1st August maybe?

I think I've mentioned it in the past: We should postpone anything
which is not a breaking change to 3.1, we have more than enough
awesome stuff for 3.0 already.

I think nobody took a look at the issues - we have simple feature
proposals from 2012 in there, sho, should they really block 3.0?

Ronny, things like "Support for Python 3.4 unittest subtests" or "drop
argparse" are marked as "critical" (mostly by you) - what's so
critical about them? To me, critical would imply we can under no
circumstances release 3.0 without that. "pytest deletes my project
files" would be critical. Feature proposals (sometimes years old)
really aren't...

> Speaking of the EuroPython sprints, is anybody going to be there to
> organise a py.test sprint?  Raphael might still be (but then he might
> want to defect to cookiecutter), Florian as well not sure about
> others?  Anyone want to volunteer leading a sprint?


I'll be there on Saturday and maaaybe Sunday morning, but chances are
I'm going to sprint on pylint again.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
> 
> 
> Floris
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
> 

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160715/7fb8a219/attachment.sig>

From brianna.laugher at gmail.com  Sat Jul 16 02:06:49 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Sat, 16 Jul 2016 16:06:49 +1000
Subject: [pytest-dev] Dependency CI
Message-ID: <CAPjwCjuTpGLfN2jBrnrNLGFCz8oKdNGqxWXWsYnXjQTOS85y5Q@mail.gmail.com>

Hi,

This is a new service thing that is free for open source projects.
https://dependencyci.com/

Is it worth investigating for pytest and plugins?

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/20160716/00aab1fb/attachment.html>

From me at the-compiler.org  Sat Jul 16 04:15:29 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Sat, 16 Jul 2016 10:15:29 +0200
Subject: [pytest-dev] Dependency CI
In-Reply-To: <CAPjwCjuTpGLfN2jBrnrNLGFCz8oKdNGqxWXWsYnXjQTOS85y5Q@mail.gmail.com>
References: <CAPjwCjuTpGLfN2jBrnrNLGFCz8oKdNGqxWXWsYnXjQTOS85y5Q@mail.gmail.com>
Message-ID: <20160716081529.wc5qoh7fj5zda4zn@tonks>

* Brianna Laugher <brianna.laugher at gmail.com> [2016-07-16 16:06:49 +1000]:
> This is a new service thing that is free for open source projects.
> https://dependencyci.com/
> 
> Is it worth investigating for pytest and plugins?

I've tried it and it didn't detect my requirements.txt
(requirements-foo.txt in a subfolder), nor does it do dependencies
from tox.ini I think.

I'm a happy user of www.requires.io though, which is Python-specific
and does both of those things ;)

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160716/1bf2ffd0/attachment.sig>

From oliver at bestwalter.de  Sun Jul 17 15:38:33 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Sun, 17 Jul 2016 19:38:33 +0000
Subject: [pytest-dev] Postpone 3.0?
In-Reply-To: <20160715160035.ibbkauceoetoogdg@tonks>
References: <CA+RQFfck93UPqdfaqXR1QXHBrV+SJqkkubNdBa8n=R1A07qP=A@mail.gmail.com>
 <CAPjwCjs2oHPZUxQ_JikB267SV=0J5TOOSaV8nMjyPSk63+GWYA@mail.gmail.com>
 <CAAWk_DxOdm9=ftBv4JVjBknBKELN8jR3UGFhrnOCu1uEXoTcTw@mail.gmail.com>
 <20160715160035.ibbkauceoetoogdg@tonks>
Message-ID: <CAG5CgtoO9x2q6eNcf3LTc1jsgVEb8Vp47vy_12vn66+WJN+zpA@mail.gmail.com>

Hi all,

I just opened a PR adding the docs about our backwards compatibility
policy: https://github.com/pytest-dev/pytest/pull/1736

With that PR all necessary elements are in place as discussed (internal
pytest warnings on by default, possibility to silence these warnings,
documentation explaining the policy).

I created it against the features branch as I am not sure if the
documentation restructuring will make it into 3.0

Cheers
Oliver

On Fri, 15 Jul 2016 at 18:06 Florian Bruhin <me at the-compiler.org> wrote:

> * Floris Bruynooghe <flub at devork.be> [2016-07-15 15:29:18 +0100]:
> > On 14 July 2016 at 23:45, Brianna Laugher <brianna.laugher at gmail.com>
> wrote:
> > > It's mainly Floris, Oliver and me that are the hold up right? Removing
> > > reinterpret assert and 2x docs.
> >
> > Reinterpret is now removed as of this morning!  I should do one more
> > PR with some doc updates.  Is that fine to do against current docs in
> > the repo for the doc-reorg?
> >
> > The milestone (https://github.com/pytest-dev/pytest/milestone/2) has a
> > lot of things still outstanding.  I'm happy to postpone, we could aim
> > for the end of the EuroPython sprints?  (although I won't be around
> > for that weekend)  Or maybe a week later even as sprints probably
> > introduce some instability.  So I'd say aim for 1st August maybe?
>
> I think I've mentioned it in the past: We should postpone anything
> which is not a breaking change to 3.1, we have more than enough
> awesome stuff for 3.0 already.
>
> I think nobody took a look at the issues - we have simple feature
> proposals from 2012 in there, sho, should they really block 3.0?
>
> Ronny, things like "Support for Python 3.4 unittest subtests" or "drop
> argparse" are marked as "critical" (mostly by you) - what's so
> critical about them? To me, critical would imply we can under no
> circumstances release 3.0 without that. "pytest deletes my project
> files" would be critical. Feature proposals (sometimes years old)
> really aren't...
>
> > Speaking of the EuroPython sprints, is anybody going to be there to
> > organise a py.test sprint?  Raphael might still be (but then he might
> > want to defect to cookiecutter), Florian as well not sure about
> > others?  Anyone want to volunteer leading a sprint?
>
>
> I'll be there on Saturday and maaaybe Sunday morning, but chances are
> I'm going to sprint on pylint again.
>
> Florian
>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
> >
> >
> > Floris
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
> _______________________________________________
> 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/20160717/ab7fef10/attachment.html>

From nicoddemus at gmail.com  Tue Jul 19 18:27:03 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 19 Jul 2016 22:27:03 +0000
Subject: [pytest-dev] EuroPython Talk on pytest 3.0
In-Reply-To: <CAG5CgtpgnW1Js55F2QP+NvaG=DOEyaCjdnm6Uk+HtjYLBQ0GSA@mail.gmail.com>
References: <D2FA6C41-F5FD-4E75-9995-BB32B6F319BB@hackebrot.de>
 <85A3678C-A51C-45F6-A45F-1754AB83C785@florian-schulze.net>
 <CAG5CgtpgnW1Js55F2QP+NvaG=DOEyaCjdnm6Uk+HtjYLBQ0GSA@mail.gmail.com>
Message-ID: <CA+RQFfdquXcW1dYZZcKP7aNjh3z7gOPaHGxLyPAzpFHf=dQ=Yg@mail.gmail.com>

Raphael,

Make sure to send us the link to your talk when it becomes available! :)

Cheers,
Bruno

On Mon, Jul 11, 2016 at 9:49 AM Oliver Bestwalter <oliver at bestwalter.de>
wrote:

> Hi,
>
> let's keep the #dropthedot in mind for the release that's really funny :D
>
> @Florian - sorry I can't remember something specific. I compiled the
> release list from the etherpad (https://pad.riseup.net/p/6pMxJxjNeFEL) -
> I hope I didn't overlook anything - maybe have a quick look if I just
> didn't process something correctly. The only other thing I remember is that
> we discussed about the warnings and thought about integrating
> pytest-warnings into core to have better filtering options - only we didn't
> think it's realistic for 3.0 so this won't be it I guess, but maybe it
> triggers your memory.
>
> About my bit on the list: I hope to compile the deprecations docs today
> and send a PR so that there is some time left to review them. @Brianna - I
> am not quite sure where I should place the docs as the restructuring is in
> process as well. Can you give me a quick hint? Oterrwise I'll just do the
> PR against features branch in the unrestructured docs first.
>
> Cheers
> Oliver
>
> On Sat, 9 Jul 2016 at 11:25 Florian Schulze <mail at florian-schulze.net>
> wrote:
>
>> During one of the discussions I agreed to work on a small bit. Problem
>> is, I didn't make a note and can't remember and I'm not on the list in
>> the wiki
>> (https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist). Does
>> anyone remember?
>>
>> Regards,
>> Florian Schulze
>>
>>
>> On 8 Jul 2016, at 21:59, Raphael Pierzina wrote:
>>
>> > Hi pytest-friends,
>> >
>> > as we are getting closer to EuroPython and my talk on Pytest 3.0, I
>> > would be delighted if you could send me your ideas on what you feel is
>> > most important to cover. I will be spending the weekend to work on my
>> > talk and send around what I have early next week.
>> >
>> > https://ep2016.europython.eu/conference/talks/pytest-30
>> > <https://ep2016.europython.eu/conference/talks/pytest-30>
>> >
>> > Holger sent around a list of features/improvement that we hope to ship
>> > with pytest (and tox); search for ?[pytest-dev] pytest-3.0 / tox-2.4
>> > release plans? from 25 June. What?s the current status and what do
>> > you think will be merged in the next couple of days to be included in
>> > the release?
>> >
>> > Any feedback or questions, please let me know.
>> >
>> > Cheers
>> > Raphael_______________________________________________
>> > 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
>>
> _______________________________________________
> 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/20160719/c8bf19ae/attachment.html>

From rpfannsc at redhat.com  Wed Jul 20 10:59:40 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 20 Jul 2016 16:59:40 +0200
Subject: [pytest-dev] can we remove the deprecated pytest.config variable
 assignment before 3.0
Message-ID: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>

Hi,

while working on config.py

i just noted we have that pytest.config assignment around in there for
compatibility
i'd like to remove it - and wonder if its something thats ok to slip into
3.0 or if we should go for deprecation in the 3 series and removal in the 4
series?

-- Ronny

-- 

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160720/5e4e279a/attachment.html>

From nicoddemus at gmail.com  Wed Jul 20 12:15:46 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 20 Jul 2016 16:15:46 +0000
Subject: [pytest-dev] can we remove the deprecated pytest.config
 variable assignment before 3.0
In-Reply-To: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>
References: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>
Message-ID: <CA+RQFfckKPtwn9avQRA3gKHsKLp=czoKRobAsyuVNyiWdjmZ6g@mail.gmail.com>

Hi Ronny,

AFAIK there?s no simple way to workaround it, correct? For example, I
believe there might be code out there using pytest.config as a conditional
in a pytest.mark.skipif decorator. In this case the change is not a simple
find/replace.

As a general guideline for deprecation vs removal, IMHO we should weight
the pain to users vs what simplifies maintenance burden for us. If the
assignment is simple to maintain, I would prefer to deprecate it in 3.0 and
remove it on 4.0.

Cheers,
?

On Wed, Jul 20, 2016 at 12:59 PM Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

> Hi,
>
> while working on config.py
>
> i just noted we have that pytest.config assignment around in there for
> compatibility
> i'd like to remove it - and wonder if its something thats ok to slip into
> 3.0 or if we should go for deprecation in the 3 series and removal in the 4
> series?
>
> -- Ronny
>
> --
>
> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander
>
> _______________________________________________
> 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/20160720/7a2c2c0e/attachment.html>

From holger at merlinux.eu  Wed Jul 20 15:50:41 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 20 Jul 2016 21:50:41 +0200
Subject: [pytest-dev] can we remove the deprecated pytest.config
 variable assignment before 3.0
In-Reply-To: <CA+RQFfckKPtwn9avQRA3gKHsKLp=czoKRobAsyuVNyiWdjmZ6g@mail.gmail.com>
References: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>
 <CA+RQFfckKPtwn9avQRA3gKHsKLp=czoKRobAsyuVNyiWdjmZ6g@mail.gmail.com>
Message-ID: <20160720195041.GB3248@uwanda>

On Wed, Jul 20, 2016 at 16:15 +0000, Bruno Oliveira wrote:
> Hi Ronny,
> 
> AFAIK there?s no simple way to workaround it, correct? For example, I
> believe there might be code out there using pytest.config as a conditional
> in a pytest.mark.skipif decorator. In this case the change is not a simple
> find/replace.

You can use string-evaluation to get access to pytest's config:

    @pytest.mark.skipif("config.option.something == 'none'")
    ...

Are there occassions where pytest.config is used during import time?
Many of them?

FWIW it's in any case possible to provide a backward-compat plugin
which makes pytest.config available i guess.

holger

 
> As a general guideline for deprecation vs removal, IMHO we should weight
> the pain to users vs what simplifies maintenance burden for us. If the
> assignment is simple to maintain, I would prefer to deprecate it in 3.0 and
> remove it on 4.0.
> 
> Cheers,
> ?
> 
> On Wed, Jul 20, 2016 at 12:59 PM Ronny Pfannschmidt <rpfannsc at redhat.com>
> wrote:
> 
> > Hi,
> >
> > while working on config.py
> >
> > i just noted we have that pytest.config assignment around in there for
> > compatibility
> > i'd like to remove it - and wonder if its something thats ok to slip into
> > 3.0 or if we should go for deprecation in the 3 series and removal in the 4
> > series?
> >
> > -- Ronny
> >
> > --
> >
> > Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
> > Commercial register: Amtsgericht Muenchen, HRB 153243,
> > Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander
> >
> > _______________________________________________
> > 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


From flub at devork.be  Wed Jul 20 17:31:16 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Wed, 20 Jul 2016 23:31:16 +0200
Subject: [pytest-dev] can we remove the deprecated pytest.config
 variable assignment before 3.0
In-Reply-To: <20160720195041.GB3248@uwanda>
References: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>
 <CA+RQFfckKPtwn9avQRA3gKHsKLp=czoKRobAsyuVNyiWdjmZ6g@mail.gmail.com>
 <20160720195041.GB3248@uwanda>
Message-ID: <CAAWk_DzNWaGiKJEOVwaFwr=DOhaVVdS0sY=NLesF-4rzY_JPtA@mail.gmail.com>

On 20 July 2016 at 21:50, holger krekel <holger at merlinux.eu> wrote:
> On Wed, Jul 20, 2016 at 16:15 +0000, Bruno Oliveira wrote:
>> Hi Ronny,
>>
>> AFAIK there?s no simple way to workaround it, correct? For example, I
>> believe there might be code out there using pytest.config as a conditional
>> in a pytest.mark.skipif decorator. In this case the change is not a simple
>> find/replace.
>
> You can use string-evaluation to get access to pytest's config:
>
>     @pytest.mark.skipif("config.option.something == 'none'")
>     ...

I'm probably with Bruno on this, seems like we might break too many test suites.

As I don't like the string version very much I was wondering if this
could take a callable instead of a bool value or a string to evaluate.
It could then optionally request "config" like other hooks work.

From nicoddemus at gmail.com  Wed Jul 20 18:47:46 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 20 Jul 2016 22:47:46 +0000
Subject: [pytest-dev] can we remove the deprecated pytest.config
 variable assignment before 3.0
In-Reply-To: <CAAWk_DzNWaGiKJEOVwaFwr=DOhaVVdS0sY=NLesF-4rzY_JPtA@mail.gmail.com>
References: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>
 <CA+RQFfckKPtwn9avQRA3gKHsKLp=czoKRobAsyuVNyiWdjmZ6g@mail.gmail.com>
 <20160720195041.GB3248@uwanda>
 <CAAWk_DzNWaGiKJEOVwaFwr=DOhaVVdS0sY=NLesF-4rzY_JPtA@mail.gmail.com>
Message-ID: <CA+RQFfd2vQza2sx3z1xZNO_7tgMn1XDh2WLt_Tm6JwweW07Ztw@mail.gmail.com>

On Wed, Jul 20, 2016 at 6:31 PM Floris Bruynooghe flub at devork.be
<http://mailto:flub at devork.be> wrote:

On 20 July 2016 at 21:50, holger krekel <holger at merlinux.eu> wrote:
> > On Wed, Jul 20, 2016 at 16:15 +0000, Bruno Oliveira wrote:
> >> Hi Ronny,
> >>
> >> AFAIK there?s no simple way to workaround it, correct? For example, I
> >> believe there might be code out there using pytest.config as a
> conditional
> >> in a pytest.mark.skipif decorator. In this case the change is not a
> simple
> >> find/replace.
> >
> > You can use string-evaluation to get access to pytest's config:
> >
> >     @pytest.mark.skipif("config.option.something == 'none'")
> >     ...
>
> I'm probably with Bruno on this, seems like we might break too many test
> suites.
>
I took a look and it seems the code involved is just this piece in main.py:

def pytest_configure(config):
    pytest.config = config # compatibiltiy

If that?s the case, I would rather officially deprecate it and keep it
around a little more since those two lines are not really hurting
maintenance. :).

Any ideas on how to only issue a warning if the object is actually
accessed? I thought something like this could do the trick:

    class _DeprecatedConfig(object):

        def __init__(self, config):
            self.__config = config
            self.__warned = False

        def __getattr__(self, attr):
            result = getattr(self, self.__config)
            if not self.__warned:
                self.__config.warn('pytest.config usage has been
deprecated and will be removed in 4.0')
                self.__warned = True
            return result

    def pytest_configure(config):
        pytest.config = _DeprecatedConfig(config)

What do you guys think?
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160720/da56fa6c/attachment-0001.html>

From rpfannsc at redhat.com  Thu Jul 21 01:29:17 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Thu, 21 Jul 2016 07:29:17 +0200
Subject: [pytest-dev] can we remove the deprecated pytest.config
 variable assignment before 3.0
In-Reply-To: <CA+RQFfd2vQza2sx3z1xZNO_7tgMn1XDh2WLt_Tm6JwweW07Ztw@mail.gmail.com>
References: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>
 <CA+RQFfckKPtwn9avQRA3gKHsKLp=czoKRobAsyuVNyiWdjmZ6g@mail.gmail.com>
 <20160720195041.GB3248@uwanda>
 <CAAWk_DzNWaGiKJEOVwaFwr=DOhaVVdS0sY=NLesF-4rzY_JPtA@mail.gmail.com>
 <CA+RQFfd2vQza2sx3z1xZNO_7tgMn1XDh2WLt_Tm6JwweW07Ztw@mail.gmail.com>
Message-ID: <CAA10jzOfwJgrzCCvidyCD9HXjN5-qtt+DrVa+onJDHhXwop67g@mail.gmail.com>

Looks fabulous, turn to a PR?
Maybe move to a _pytest.deprecated plugin

Am 21.07.2016 00:47 schrieb "Bruno Oliveira" <nicoddemus at gmail.com>:
>
> On Wed, Jul 20, 2016 at 6:31 PM Floris Bruynooghe flub at devork.be wrote:
>>
>> On 20 July 2016 at 21:50, holger krekel <holger at merlinux.eu> wrote:
>> > On Wed, Jul 20, 2016 at 16:15 +0000, Bruno Oliveira wrote:
>> >> Hi Ronny,
>> >>
>> >> AFAIK there?s no simple way to workaround it, correct? For example, I
>> >> believe there might be code out there using pytest.config as a
conditional
>> >> in a pytest.mark.skipif decorator. In this case the change is not a
simple
>> >> find/replace.
>> >
>> > You can use string-evaluation to get access to pytest's config:
>> >
>> >     @pytest.mark.skipif("config.option.something == 'none'")
>> >     ...
>>
>> I'm probably with Bruno on this, seems like we might break too many test
suites.
>
> I took a look and it seems the code involved is just this piece in
main.py:
>
> def pytest_configure(config): pytest.config = config # compatibiltiy
>
> If that?s the case, I would rather officially deprecate it and keep it
around a little more since those two lines are not really hurting
maintenance. :).
>
> Any ideas on how to only issue a warning if the object is actually
accessed? I thought something like this could do the trick:
>
>  class _DeprecatedConfig(object): def __init__(self, config):
self.__config = config self.__warned = False def __getattr__(self, attr):
result = getattr(self, self.__config) if not self.__warned:
self.__config.warn('pytest.config usage has been deprecated and will be
removed in 4.0') self.__warned = True return result def
pytest_configure(config): pytest.config = _DeprecatedConfig(config)
>
> What do you guys think?
>
> ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160721/ebbca651/attachment.html>

From nicoddemus at gmail.com  Thu Jul 21 08:09:12 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 21 Jul 2016 12:09:12 +0000
Subject: [pytest-dev] can we remove the deprecated pytest.config
 variable assignment before 3.0
In-Reply-To: <CAA10jzOfwJgrzCCvidyCD9HXjN5-qtt+DrVa+onJDHhXwop67g@mail.gmail.com>
References: <CAA10jzMbgSjvP3uqosrJNjmWQuFEbcZp-BRSop1zr3+VLq84Vw@mail.gmail.com>
 <CA+RQFfckKPtwn9avQRA3gKHsKLp=czoKRobAsyuVNyiWdjmZ6g@mail.gmail.com>
 <20160720195041.GB3248@uwanda>
 <CAAWk_DzNWaGiKJEOVwaFwr=DOhaVVdS0sY=NLesF-4rzY_JPtA@mail.gmail.com>
 <CA+RQFfd2vQza2sx3z1xZNO_7tgMn1XDh2WLt_Tm6JwweW07Ztw@mail.gmail.com>
 <CAA10jzOfwJgrzCCvidyCD9HXjN5-qtt+DrVa+onJDHhXwop67g@mail.gmail.com>
Message-ID: <CA+RQFfcSEWVrBAYF8ED_x1K0OFFDm_sYBjMdH2UBcDUpAiMR2A@mail.gmail.com>

On Thu, Jul 21, 2016 at 2:29 AM Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

Looks fabulous, turn to a PR?
>
Sorry, are you asking me to do it, or if you should do it yourself? If you
could tackle that it would be great, otherwise I think I will have some
time tonight to do it.

Maybe move to a _pytest.deprecated plugin
>
Hmmm it might be useful to have this, specially as a central point to have
deprecated stuff so it is clear what should be removed when 4.0 comes
around. We don?t even need to move the entire deprecated functionality,
just put something in this deprecated plugin as a reminder.

As an example of what I mean, we recently deprecated declaring fixtures
with "pytest_funcarg__" prefix. The fixture collection code uses a variable
_argprefix to check if a function is a fixture:

            if marker is None:
                if not name.startswith(self._argprefix):
                    continue
                if not callable(obj):
                    continue
                marker = defaultfuncargprefixmarker
                name = name[len(self._argprefix):]

The suggestion would then to move self._argprefix to the deprecated plugin:

            if marker is None:
                if not name.startswith(_pytest.deprecated.argprefix):
                    continue
                if not callable(obj):
                    continue
                marker = defaultfuncargprefixmarker
                name = name[len(_pytest.deprecated.argprefix):]

By the time pytest 4.0 comes around, technically it would be a matter of
deleting the contents of _pytest.deprecated and fix what ?breaks?.

What do you guys think, is this worth having?

Thanks,
Bruno.
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160721/7fc55d90/attachment.html>