Re: [pytest-dev] pytest 5.0.0 and pluginmanager

On Mon, Jul 1, 2019 at 9:21 AM Chris Dent wrote: > On Mon, 1 Jul 2019, Bruno Oliveira wrote: > > On Mon, Jul 1, 2019 at 8:17 AM Chris Dent wrote: > > Is Gabbi + pytest a plugin? If so, you could store the config object > during > > pytest_configure to reuse later:

Re: [pytest-dev] pytest 5.0.0 and pluginmanager

Hi Chris, On Mon, Jul 1, 2019 at 8:17 AM Chris Dent wrote: > > That uses the now deprecated `pytest.config` global and I'm > struggling to determine how best to replace it without having to > make changes to the calling patterns that would break compatibility > with existing test installations.

Re: [pytest-dev] Indeed.com FOSS Contributor Fund and OpenCollective

Hey everyone, I've open a PR adding information about OpenCollective and Tidelift to the docs: https://github.com/pytest-dev/pytest/pull/5527 I've added a few maintainers as reviewers, but everybody is encouraged to comment. Cheers, Bruno On Thu, Jun 27, 2019 at 6:55 PM Bruno Oliveira wrote

[pytest-dev] Indeed.com FOSS Contributor Fund and OpenCollective

Hi everyone! Recently pytest has been elected to receive a donation from Indeed.com, in their FOSS contributor fund initiative. On it, each month open source contributors who work at Indeed get the opportunity to vote for a project which will receive a monetary donation. Contributors for May have

[pytest-dev] class-based markers API discussion

Hi everyone, We have started a discussion over Ronny's proposal of using class-based markers at https://github.com/pytest-dev/pytest/issues/5424, everyone is welcome to join. (Sending an email here as many people don't follow GitHub discussions closely and will probably miss that). Cheers,

Re: [pytest-dev] Other plugin breaking usage of pytest-cache

Hi Elijah, On Thu, May 16, 2019 at 6:29 PM Elijah DeLee wrote: > Reference issue: https://github.com/ansible/pytest-mp/issues/18 > > > I'm having trouble knowing where to start looking. Can anyone give me a > clue at what point the tests get recorded into the cache? > The last-failed support

[pytest-dev] pytest 4.5

Sottile * Bruno Oliveira * Daniel Hahler * Floris Bruynooghe * Pulkit Goyal * Samuel Searles-Bryant * Zac Hatfield-Dodds Happy testing, The Pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo

Re: [pytest-dev] [core] Tidelift Funding

, On Wed, May 8, 2019 at 8:05 AM Bruno Oliveira wrote: > Hey Daniel, > > On Wed, May 8, 2019 at 5:57 AM Daniel Hahler > wrote: > >> >> I think a new repository like pytest-meta, or pytest-org makes sense - it >> is >> easy to setup in general, and keeps

[pytest-dev] pytest 4.4.2

: * Allan Lewis * Anthony Sottile * Bruno Oliveira * DamianSkrzypczak * Daniel Hahler * Don Kirkby * Douglas Thor * Hugo * Ilya Konstantinov * Jon Dufresne * Matt Cooper * Nikolay Kondratyev * Ondřej Súkup * Peter Schutt * Romain Chossart * Sitaktif Happy testing, The pytest Development Team

Re: [pytest-dev] [core] Tidelift Funding

Hey Daniel, On Wed, May 8, 2019 at 5:57 AM Daniel Hahler wrote: > > I think a new repository like pytest-meta, or pytest-org makes sense - it > is > easy to setup in general, and keeps away noise from the main repo. > > We could create some issue in the main repo to link to it for transparency.

Re: [pytest-dev] [core] Tidelift Funding

On Tue, May 7, 2019 at 3:20 PM Floris Bruynooghe wrote: > On Mon 06 May 2019 at 23:58 +0200, Ronny Pfannschmidt wrote: > > > we should make a git repo where we track meta level documentation, > > that way we chould have a ci with credentials run the checks > > +1 to tracking this in a text file

Re: [pytest-dev] [core] Tidelift Funding

Hi Floris, On Thu, May 2, 2019 at 2:25 PM Floris Bruynooghe wrote: > Why the rules about active? Seems complicated and more open to > arguing. I liked the Pillow guidelines you linked: > https://github.com/orgs/pytest-dev/teams/contributors can express > interest and

Re: [pytest-dev] pytest slack reporting plugin proposal

probably to update links, badges, etc to the new URL. Welcome! :) Cheers > > чт, 2 мая 2019 г. в 21:38, Bruno Oliveira : > >> Hi everyone >> >> On Thu, May 2, 2019 at 3:27 PM Arseniy Antonov >> wrote: >> >>> >>> Please tell me what I should

Re: [pytest-dev] pytest slack reporting plugin proposal

Hi everyone On Thu, May 2, 2019 at 3:27 PM Arseniy Antonov wrote: > > Please tell me what I should do next by the process. > Thanks Arseniy for the interest. The steps are written here: https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev

Re: [pytest-dev] [core] Tidelift Funding

Em qui, 2 de mai de 2019 04:44, Florian Bruhin escreveu: > Hey, > > On Wed, May 01, 2019 at 05:25:58PM -0300, Bruno Oliveira wrote: > > there were no obligations whatsoever after joining the platform other > than > > "maintain the project", which they

[pytest-dev] [core] Tidelift Funding

Hi core maintainers, Half a year ago Keenan Szulik from Tidelift reached me and Holger about the possibility of pytest joining Tidelift for funding. At first our answer was "not right now" for two reasons: we didn't actually knew the platform (for example what expect in terms of obligations) and

[pytest-dev] Pytest 4.4.1 released!

: * Anthony Sottile * Bruno Oliveira * Daniel Hahler Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 4.4 released!

Sottile * ApaDoctor * Bernhard M. Wiedemann * Brian Skinn * Bruno Oliveira * Daniel Hahler * Gary Tyler * Jeong YunWon * Miro Hrončok * Takafumi Arakaki * henrykironde * smheidrich Happy testing, The Pytest Development Team ___ pytest-dev mailing list pytest

[pytest-dev] pytest 4.3.1 bug fix release

, among them: * Andras Mitzki * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Danilo Horta * Grygorii Iermolenko * Jeff Hale * Kyle Altendorf * Stephan Hoyer * Zac Hatfield-Dodds * Zac-HD * songbowen Happy testing, The pytest Development Team ___ pytest

[pytest-dev] pytest 4.3.0 released

: * Andras Mitzki * Anthony Sottile * Bruno Oliveira * Christian Fetzer * Daniel Hahler * Grygorii Iermolenko * R. Alex Matevish * Ronny Pfannschmidt * cclauss Happy testing, The Pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https

Re: [pytest-dev] Taking a break for 3-6 Months

On Fri, Feb 15, 2019 at 12:53 PM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi Everyone, > > it came to my attention that a certain kind of fatigue has started to > sneak up on me, > as such i'm taking quite some time off my personal open-source work to > have more time for my

[pytest-dev] pytest 4.2.1 released

. This release fixes the recent problems with more-itertools 6.0 on Python 2. Thanks to all who contributed to this release, among them: * Anthony Sottile * Arel Cordero * Bruno Oliveira * Daniel Hahler * Holger Kohr * Kevin J. Foley * Nick Murphy * Paweł Stradomski * Raphael Pierzina * Ronny Pfannschmidt

[pytest-dev] pytest 4.2.0 released

* Anthony Sottile * Bruno Oliveira * Christopher Dignam * Daniel Hahler * Joseph Hunkeler * Kristoffer Nordstroem * Ronny Pfannschmidt * Thomas Hisch * wim glenn Happy testing, The Pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org

[pytest-dev] The Gentle Art Of Patch Review

Hi everyone, I noticed Nathaniel J. Smith has added this link to the trio docs recently[1]: http://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/ I got curious and indeed it is an interesting read, so I'm sharing it with the list. Cheers, Bruno. [1]:

[pytest-dev] pytest 4.1.1

: * Anthony Sottile * Anton Lodder * Bruno Oliveira * Daniel Hahler * David Vo * Oscar Benjamin * Ronny Pfannschmidt * Victor Maryama * Yoav Caspi * dmitry.dygalo Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org

[pytest-dev] pytest 4.1.0

/changelog.html For complete documentation, please visit: https://docs.pytest.org/en/latest/ As usual, you can upgrade from pypi via: pip install -U pytest Thanks to all who contributed to this release, among them: * Adam Johnson * Aly Sivji * Andrey Paramonov * Anthony Sottile * Bruno Oliveira

[pytest-dev] pytest 4.0.2

, among them: * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Pedro Algarvio * Ronny Pfannschmidt * Tomer Keren * Yash Todi Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman

Re: [pytest-dev] Using pytest for the sympy doctests

On Sun, Dec 9, 2018 at 6:27 PM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Am Sonntag, den 09.12.2018, 17:55 -0200 schrieb Bruno Oliveira: > > > > On Sun, Dec 9, 2018 at 4:35 PM Oscar Benjamin > wrote: > > It's not a huge problem. I

Re: [pytest-dev] Using pytest for the sympy doctests

Hi Oscar, On Sun, Dec 9, 2018 at 12:30 PM Oscar Benjamin wrote: > Is there any way to set those doctest option flags in conftest.py > rather than pytest.ini? > Currently those options are only possible to be set in pytest.ini, I'm afraid. Any reason why is that a problem though? Cheers, Bruno

[pytest-dev] pytest 4.0.1

: * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Michael D. Hoyle * Ronny Pfannschmidt * Slam Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 4.0.0 released!

The pytest team is proud to announce the 4.0.0 release! This version is near identical to 3.10 feature-wise, except now pytest's own deprecated features generate errors, but they can be turned back into warnings as a stop gap measure until 4.1. Users are *strongly* encouraged to take a look at

Re: [pytest-dev] pyi stubs (PEP 561/ PEP-484) for pytest

Hi Ilya, On Tue, Nov 13, 2018 at 8:19 PM Ilya Kazakevich < ilya.kazakev...@jetbrains.com> wrote: > > My name is Ilya, I develop pytest integration in PyCharm IDE. > That's great! I use PyCharm daily and it is an awesome IDE, thanks for all the work. > We can create this package by ourselves

Re: [pytest-dev] another "i have had it moment" and a stern request ro review our interaction with backward compatibility

Hi Ronny, On Wed, Nov 7, 2018 at 7:12 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > > ... > > This is an accumulative cost in many ways - in particular for a project > driven primarily by volunteers - every hour we sacrafice to this altar > of technical debt is an hour lost

Re: [pytest-dev] breaking releases required - sorting out FunctionDefinition and Compatproperties

Hi Ronny, On Wed, Nov 7, 2018 at 6:26 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > > i propose we prepare an actual breraking release since its about time > for that since quite a while. > Sure, it has been awhile and the features have been deprecated for a long time. I

[pytest-dev] pytest 3.10

Hovmöller * Andreu Vallbona Plazas * Ankit Goel * Anthony Sottile * Bernardo Gomes * Brianna Laugher * Bruno Oliveira * Daniel Hahler * David Szotten * Mick Koch * Niclas Olofsson * Palash Chatterjee * Ronny Pfannschmidt * Sven-Hendrik Haase * Ville Skyttä * William Jamir Silva Happy testing, The Pytest

[pytest-dev] pytest 3.9.3

, among them: * Andreas Profous * Ankit Goel * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Jon Dufresne * Ronny Pfannschmidt Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman

[pytest-dev] Enable "WIP" application in pytest

Hi everyone, We often have PRs that are a WIP and should not be merged. I was thinking of enabling the WIP application (https://github.com/apps/wip) for pytest-dev/pytest and see if it is useful. Any thoughts? If nobody raises concerns I intend to enable this tomorrow. :) Cheers, Bruno

[pytest-dev] pytest 3.9.2

them: * Ankit Goel * Anthony Sottile * Bruno Oliveira * Ronny Pfannschmidt * Vincent Barbaresi * ykantor Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Deprecation warnings that I didn't cause. Or did I?

Hi Vasily! On Mon, Oct 22, 2018 at 8:19 PM Vasily Kuznetsov wrote: > Hi everyone! > > Could somebody who understands the newly deprecated features take a look > at my code (there's not much, the whole extension is just 168 lines of code > in one file >

Re: [pytest-dev] Improving pytest internal errors and messages

message). > I think ReportableError is a good name, as I'm having a hard time coming up with a good name that isn't similar to UsageError/UserError. :) Cheers, Bruno. > > > On Thu, 4 Oct 2018 at 15:51 Florian Bruhin wrote: > >> Hey, >> >> On Thu, Oct 04, 2018 at 10:19:21A

[pytest-dev] Improving pytest internal errors and messages

Hi everyone, Often some errors in pytest show a long traceback with the pytest internals, which is noisy and distracting. For example, if a user makes a typo when declaring the scope of a fixture, we get an error like this: ``` = ERRORS

Re: [pytest-dev] the requirement for enabling repeated and successive api breakages

Hi Ronny, >From my POV breaking those internal APIs slowly and with warnings in place is fine, just like it was done with the "marks" API. I suspect that the internal Node creation API sees even less usage than marks, so I think it is fine to break it slowly and with proper warnings in place.

Re: [pytest-dev] Results of the "drop python 3" poll and what i envision to do about it

On Mon, Oct 1, 2018 at 8:22 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > > In the plan i outlined, the first python 3 only release would be the one > that drops 3.4 mid-2019 - at that point in time the maintenance branch > would be prepared before release merge time. > I

Re: [pytest-dev] Results of the "drop python 3" poll and what i envision to do about it

Hi Ronny, On Mon, Oct 1, 2018 at 5:01 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi Everyone, > > the python3 support poll has run its on > https://twitter.com/ossronny/status/1043837215175057408 > > The results have a interesting shape. > > 37%now > 09%with 3.4 mid

Re: [pytest-dev] branch proposals - python2 support and pytest 4.0 preps

Hi Nicholas, On Mon, Sep 24, 2018 at 11:33 AM Nicholas Williams < nicholas+pyt...@nicholaswilliams.net> wrote: > Background question: Will PyTest 4.0 be removing support for Python 2? Or > am I misunderstanding this? > No, Ronny's email address two topics: removal of currently deprecated

Re: [pytest-dev] branch proposals - python2 support and pytest 4.0 preps

Hi Ronny, On Mon, Sep 24, 2018 at 10:29 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > > a) maintenance-python2 : this will be the branch where bugfixes for the > last python2 suporting versions will happen > > i intend to create it in line with the yet to be shaped plans for

[pytest-dev] pytest Python 2.7 support (poll)

Hi everyone, There's a poll on twitter regarding when pytest should drop Python 2.7 support: https://twitter.com/ossronny/status/1043837215175057408 I urge everyone who uses pytest to cast their vote! Important to note that even when pytest drops support, Python 2.7 users will still be able to

[pytest-dev] pytest.raises message parameter

Hi everyone, When using `pytest.raises`, it seems a lot of users confuse the parameter `message` (a message to display if the with block finishes with no exception) and `match` (a regular expression that the exception should match), using the former when they meant the latter. This is very

Re: [pytest-dev] Hacktoberfest - Beginner Issues

On Thu, Sep 6, 2018 at 2:26 PM Maik Figura wrote: > Hey everyone, > > I noticed that the issue tracker almost hit 500 issues. Would it be good > to discuss how to handle issues in general (follow ups, etc) and on how > to maybe reduce the amount of outdated issues (I am not even sure there > are

[pytest-dev] pytest 3.8.0 released!

://docs.pytest.org/en/latest/ As usual, you can upgrade from pypi via: pip install -U pytest Thanks to all who contributed to this release, among them: * Anthony Sottile * Bruno Oliveira * CrazyMerlyn * Daniel Hahler * Fabio Zadrozny * Jeffrey Rackauckas * Ronny Pfannschmidt * Virgil Dupras * dhirensr

Re: [pytest-dev] pytest Quick Start Guide

Thanks a lot Oliver, it means a lot! Em qui, 30 de ago de 2018 12:32, Oliver Bestwalter escreveu: > H Bruno, > > congratulations! Bought it right away - coming from you it has to be good > :) > > Cheers, > Oliver > > On Thu, 30 Aug 2018 at 17:09 Bruno Olivei

[pytest-dev] pytest Quick Start Guide

Hi everyone, I'm pleased to announce the release of my book about pytest: https://www.packtpub.com/web-development/pytest-quick-start-guide I cover how to get started quickly to use pytest in your daily work, and some more niche topics like techniques to convert unittest-based suites to pytest.

Re: [pytest-dev] sorting out broken config initialization - by doing major releases with api breakages

Hi Floris, On Tue, Aug 21, 2018 at 6:02 PM Floris Bruynooghe wrote: > On Tue 21 Aug 2018 at 11:03 -0300, Bruno Oliveira wrote: > > Personally my next goal is the task to replace the internal warnings > system > > to use the standard warnings module, which I should be abl

Re: [pytest-dev] sorting out broken config initialization - by doing major releases with api breakages

On Tue, Aug 21, 2018 at 9:14 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi Bruno, > > i created https://github.com/pytest-dev/pytest/projects/2 as a starting > point a while back, > but its still far from the botton of things, > > My current impression is, that a detailed

Re: [pytest-dev] sorting out broken config initialization - by doing major releases with api breakages

Hi Ronny, On Tue, Aug 21, 2018 at 4:00 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi everyone, > > currently pytest configguration initialization is pretty much broken in > many details, > and as far as i can tell its going to be even more tricky to try and fix > than

[pytest-dev] pytest 3.7.2 released

: * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Josh Holland * Ronny Pfannschmidt * Sankt Petersbug * Wes Thomas * turturica Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman

Re: [pytest-dev] junitxml update

Hey, On Sat, Aug 18, 2018 at 9:17 AM Floris Bruynooghe wrote: > Hi Rusty, > > On Fri 17 Aug 2018 at 22:08 -0600, Rusty Howell wrote: > > > In doing some research on this, I see that the py library is in > maintenance > > mode and "should not be used in new code", according to the docs at > >

Re: [pytest-dev] junitxml update

that this can become a problem. But I could be wrong of course. Rusty, Would love to also hear your thoughts about all this! Cheers, Bruno. > > moving forward i'll consider xunit as something i will not touch. > > -- Ronny > > Am 16.08.2018 um 14:04 schrieb Bruno Oliveira: &g

Re: [pytest-dev] junitxml update

Hi folks, On Thu, Aug 16, 2018 at 2:19 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi Rusty, > > my basic idea to move it forward is to remove it from the pytest core so > it has freedom to evolve, > and then getting interested parties to actually work on it as they see fit.

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

Feel free to add me as well Florian. []s On Sat, Aug 4, 2018 at 8:58 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi, > > pytest+...@ronnypfannschmidt.de > > -- Ronny > > Am 04.08.2018 um 10:50 schrieb Florian Bruhin: > > On Tue, Jul 31, 2018 at 12:53:51PM +0100, Dave Hunt

Re: [pytest-dev] Partnership possibility with Pytest

Hi all, On Tue, Jul 31, 2018 at 3:28 PM Floris Bruynooghe wrote: > Hi, > > On Mon 30 Jul 2018 at 23:14 -0700, Alex Georgie wrote: > [...] > > *How it works* > > > > We provide you a script that you add to the Pytest site. That script > makes > > a call to our site to create a 'drop' every 2

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

Howdy, On Tue, Jul 31, 2018 at 3:51 PM Florian Bruhin wrote: > I was initially sceptical about CoCs in general as well, but after > spending months researching the topic from both sides and talking to a > lot of people, it got clear to me that CoCs are a very good thing - > even/especially in

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

Hi Dave, On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt wrote: > I’d like to add a code of conduct for my pytest plugins, and as they’re > mostly under the pytest organisation on GitHub I thought it would make > sense to use the same as the pytest project. I was surprised to find that > the pytest

[pytest-dev] pytest 3.7.0 released!

* Alan Brammer * Ammar Najjar * Anthony Sottile * Bruno Oliveira * Jeffrey Rackauckas * Kale Kundert * Ronny Pfannschmidt * Serhii Mozghovyi * Tadek Teleżyński * Wil Cooley * abrammer * avirlrma * turturica Happy testing, The Pytest Development Team

Re: [pytest-dev] Disable pushing directly to features and master branches

Thanks everyone for their input, it is enabled now! On Fri, Jul 6, 2018 at 9:54 PM Oliver Bestwalter wrote: > sounds good. > On Fri 6. Jul 2018 at 20:43, Floris Bruynooghe wrote: > >> On Fri 06 Jul 2018 at 12:13 -0300, Bruno Oliveira wrote: >> > GitHub has started issue

Re: [pytest-dev] [PROPOSAL] switchgin over from gitmate via pytestbot to gitmate as an github app

Hi Ronny, (Missed this email somehow) Are there any visible differences, aside from the comments being made by some GitMade bot account instead of pytestbot? Cheers On Sun, Jul 1, 2018 at 9:24 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi everyone, > > im considering

[pytest-dev] Disable pushing directly to features and master branches

Hi everyone, GitHub has started issue warnings that the email service we use to notify pushes to master and features will be discontinued (and we suspect it is not working correctly either). Given that we now invite people who have have had a complete PR merged, a lot of new people are getting

Re: [pytest-dev] New pytest plugin: pytest-cases

Hi Sylvain, Interesting plugin, I like the idea of lazy data generation for parametrize! Thanks for sharing on the list. Cheers, Bruno. On Thu, Jul 5, 2018 at 3:33 PM Sylvain MARIE < sylvain.ma...@schneider-electric.com> wrote: > Hello dear pytest community members > > > > A small email to

[pytest-dev] pytest 3.6.3

: * AdamEr8 * Anthony Sottile * Bruno Oliveira * Jean-Paul Calderone * Jon Dufresne * Marcelo Duarte Trevisani * Ondřej Súkup * Ronny Pfannschmidt * T.E.A de Souza * Victor * victor Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest

[pytest-dev] pytest 3.6.1

: * Anthony Sottile * Bruno Oliveira * Jeffrey Rackauckas * Miro Hrončok * Niklas Meinzer * Oliver Bestwalter * Ronny Pfannschmidt Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman

[pytest-dev] pytest 3.6.0 released!

visit: http://docs.pytest.org As usual, you can upgrade from pypi via: pip install -U pytest Thanks to all who contributed to this release, among them: * Anthony Shaw * ApaDoctor * Brian Maissy * Bruno Oliveira * Jon Dufresne * Katerina Koukiou * Miro Hrončok * Rachel Kogan * Ronny

Re: [pytest-dev] Refactor the old tests with pytest

tems > > > > > > > > > > > Thanks Bruno and PYTEST!! > > On Fri, May 11, 2018 at 8:56 PM, Reed Xia <huaqin2...@gmail.com> wrote: > >> Wow.. sound great! Thanks Bruno, I'll check! >> &

Re: [pytest-dev] Refactor the old tests with pytest

Hi Reed, You should take a look at parametrizing[1] so you end up with only: /api_test test_device_api01.py test_device_api02.py test_device_api03.py And inside it all tests are parametrized based on LAN_URL and WAN_URL (possibly using a parametrized fixture if it is more convenient).

Re: [pytest-dev] request to add pytest-echo to pytest-dev plugins

Thanks Floris! Stefano feel free to transfer the repository to me (@nicoddemus) or Floris (@flub) and we can complete the transfer! Cheers, On Tue, May 1, 2018 at 5:17 PM Floris Bruynooghe <f...@devork.be> wrote: > +1 from me too :) > > On Sun 29 Apr 2018 at 16:39 +, Bruno

Re: [pytest-dev] request to add pytest-echo to pytest-dev plugins

Hi Stefano, The plugin meets all requirements so +1 from me. :) Cheers On Sat, Apr 28, 2018 at 2:18 PM Stefano wrote: > Hi, > > I did a very small plugin (pytest-echo), let me know if it can be added > to the pytest-dev organization. > > Code can be found at

[pytest-dev] pytest 3.5.1 released

: * Brian Maissy * Bruno Oliveira * Darren Burns * David Chudzicki * Floris Bruynooghe * Holger Kohr * Irmen de Jong * Jeffrey Rackauckas * Rachel Kogan * Ronny Pfannschmidt * Stefan Scherfke * Tim Strazny * Семён Марьясин Happy testing, The pytest Development Team

Re: [pytest-dev] new pytest-dev plugin proposal

Hi Davide, +1 to both. Now we need another +1 from some other core dev to start the transferring process. :) Cheers, Bruno. On Thu, Apr 12, 2018 at 4:46 AM davide moro wrote: > Hi, > > I asked permission to my company for transferring the ownership of github >

Re: [pytest-dev] Pytest hoodie

Hi Oleg, That's awesome, thanks for sharing! :) Welcome to the project! Cheers, On Wed, Mar 28, 2018 at 10:11 AM Oleg S wrote: > Hi all! > I printed pytest hoodie :D > > Please, follow these links for images: > https://sun9-4.userapi.com/c831508/v831508192/beec8/HthxTa1did4.jpg

Re: [pytest-dev] pytest-flask maintainer unreachable

my best and sorry for a long delay in responses. > > Cheers, > Vital. > > On Tue, Mar 27, 2018 at 2:02 PM Bruno Oliveira <nicodde...@gmail.com> > wrote: > >> Hi everyone, >> >> People have expressed concern over pytest-flask because there has not >>

[pytest-dev] pytest-flask maintainer unreachable

Hi everyone, People have expressed concern over pytest-flask because there has not been a release in over 2 years (see https://github.com/pytest-dev/pytest-flask/issues/72) and Vital Kudzelka (the maintainer) has not been active in the repository for some time, with PRs waiting to be merged.

[pytest-dev] pytest 3.5.0 released!

://doc.pytest.org/en/latest/changelog.html For complete documentation, please visit: http://docs.pytest.org As usual, you can upgrade from pypi via: pip install -U pytest Thanks to all who contributed to this release, among them: * Allan Feldman * Brian Maissy * Bruno Oliveira * Carlos Jenkins

Re: [pytest-dev] License for pytest-dev/pytest-design

this though... > > As for contributors, Brianna also contributed quite a lot during the > sprint and "asserts before reverts" motto is her idea if I remember it > right. > > Cheers, > Vasily > > On Sat, Mar 17, 2018 at 12:02 AM Floris Bruynooghe <f...@devork.be> w

Re: [pytest-dev] Fixture ordering and scopes

Howdy! On Thu, Mar 15, 2018 at 6:42 PM Bruno Oliveira <nicodde...@gmail.com> wrote: > I opened up a PR <https://github.com/pytest-dev/pytest/pull/3306> which > does sort parameters by scope while keeping the relative order of fixtures > of same scope intact, and the test

Re: [pytest-dev] Fixture ordering and scopes

On Tue, Mar 20, 2018 at 10:45 AM Floris Bruynooghe <f...@devork.be> wrote: > On Tue, Mar 20 2018, Bruno Oliveira wrote: > > > > @pytest.fixture(scope='session', autouse=True) > > def my_setup_logging(log_setup): pass > > > > @pytest.fixture(scope='sess

Re: [pytest-dev] Fixture ordering and scopes

On Sat, Mar 17, 2018 at 6:38 PM Floris Bruynooghe wrote: > > I'm still not following this, I'm probably being silly. You have 4 > autouse session-scoped fixtures but with a dependecy chain as > my_db_setup -> my_setup_logging -> setup_logging and then an unrelated > db_setup.

Re: [pytest-dev] No traceback filtering with __tracebackhide__ attribute using custom pytest plugin

Hi Ringo, I would expect the basic traceback filtering to work via the runner, > irrespective of which custom tests a thirdparty plugin provides. What do I > consider basic filtering? Filtering out the traceback entries of the runner > as defined in python.py:filter_traceback function (pluggy,

[pytest-dev] License for pytest-dev/pytest-design

Hi folks, pytest-design is the repository used to store logo and t-shirt designs from our 2016 sprint, but it currently it isn't under any LICENSE. I've been asked if it was OK to use the logos to make a t-shirt (and of course I know it is), but we should add a license to the repository allowing

Re: [pytest-dev] Fixture ordering and scopes

On Fri, Mar 16, 2018 at 2:36 PM Floris Bruynooghe <f...@devork.be> wrote: > Bruno Oliveira <nicodde...@gmail.com> writes: > > > So the order is important here, and leaving it undefined will require > > people to write this instead: > > > > @pytest.fixt

Re: [pytest-dev] pytest-commit emails

Oh OK, thanks Floris. Weird, I don't receive emails from Ronny it seems, he merged some PRs this week but I didn't receive anything. Cheers, Bruno. On Fri, Mar 16, 2018 at 3:18 PM Floris Bruynooghe <f...@devork.be> wrote: > Bruno Oliveira <nicodde...@gmail.com> writes: >

Re: [pytest-dev] pytest-commit emails

On Fri, Mar 16, 2018 at 5:23 AM Floris Bruynooghe <f...@devork.be> wrote: > Bruno Oliveira <nicodde...@gmail.com> writes: > > > Hi everyone, > > > > I receive an email from pytest-com...@python.org whenever new merges > happen > > on a branch of the py

Re: [pytest-dev] Fixture ordering and scopes

Hi Vasily! On Fri, Mar 16, 2018 at 7:17 AM Vasily Kuznetsov wrote: > I very much agree with Floris that if you need fixture A to run before > fixture B and otherwise things break, this is called "dependency" and it's > better if it's explicitly declared. > Definitely, if a

Re: [pytest-dev] Fixture ordering and scopes

Hi Floris, On Fri, Mar 16, 2018 at 5:42 AM Floris Bruynooghe <f...@devork.be> wrote: > Bruno Oliveira <nicodde...@gmail.com> writes: > > > Hi everyone and Holger, > > > > Looking at the code below: > > > > > > data = {} > > @pytest.

Re: [pytest-dev] preparing a breaking internal change - splitting Session into the node and the plugin

Hi everyone, On Fri, Mar 9, 2018 at 10:46 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > > > I wouldn't take a major release to cram in as much changes as possible. > > IMHO it's fine to have a major release for just one breaking change. > > That way it's easier to manage

[pytest-dev] Fixture ordering and scopes

Hi everyone and Holger, Looking at the code below: data = {} @pytest.fixture(scope='session')def clean_data(): data.clear() @pytest.fixture(autouse=True)def add_data(): data['value'] = 1 @pytest.mark.usefixtures('clean_data')def test_foo(): assert data.get('value') Should test_foo

Re: [pytest-dev] pytest 3.5 soon?

On Thu, Mar 15, 2018 at 4:26 PM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > +1 > > the next big things i will try to work on are > > * a new marker api and > * a actually correct config initialization > (the one we currently do is broken and creates bugs in xdist) > Sounds

[pytest-dev] pytest 3.5 soon?

Hi everyone, pytest 3.4 was released on 2018-01-30, and we had agreed that we should make a new minor release every 2 months or so to allow users to enjoy the new features and fixes in the “features” branch. For 3.5 one of the major features was to replace the internal warning subsystem by the

[pytest-dev] "Reference" page is up!

Hey everyone, I've merged the PR which includes a long-time-requested Reference page, check it out at: *https://docs.pytest.org/en/latest/reference.html * It might have some missing bits still, in which case feedback is welcome! Cheers, Bruno.

[pytest-dev] pytest-commit emails

Hi everyone, I receive an email from pytest-com...@python.org whenever new merges happen on a branch of the pytest repository, but it seems it happens only for my own merges. It was my understanding I should receive for any merge, not just my own. Does this happen for anybody else or is it just

Re: [pytest-dev] Moving pytest-{pep8, flakes} to pytest-dev on GitHub

Hi Florian, On Wed, Mar 14, 2018 at 5:40 AM Florian Schulze wrote: > I'd like to propose moving pytest-pep8 from pytest-dev on Bitbucket to > GitHub and my pytest-flakes from my GitHub repository to pytest-dev. > Since I use both myself all the time, I would continue

Re: [pytest-dev] Adding intro talk/slides to pytest-dev repos and licensing

Hi all, Nice initiative Floris and Ronny! I definitely like the idea of having a set of talks and introductions so more people are encouraged to give talks and teach pytest, from local group meetings to bigger conferences. Cheers, Bruno On Wed, Mar 14, 2018 at 2:33 AM RonnyPfannschmidt <

<    1   2   3   4   5   >