Re: [pytest-dev] pytest documentation

I'm still in favour, and it sounds like a smart way to avoid the problems of a long-lived branch. On Wed, 3 Mar 2021 at 07:57, Daniele Procida wrote: > Bruno Oliveira wrote: > > >I definitely think it would be a good idea, but I'm interested to hear > >what the other maintainers think as well.

[pytest-dev] Manually running test steps/getting user input

I work in an environment where there is a lot of manual text execution (blame hardware). Moving people to ATDD/BDD style tests (such as Gherkin) is a first step. The good thing about tests written in this style is it works for both automated and manual execution. We are looking at adopting such

[pytest-dev] Resolution of recent conflict

Many of you know that there has recently been some conflict within the pytest core maintainer group. Thanks all for your patience while discussions took place in the background. In the end, we as active maintainers agreed to exclude Daniel from pytest project membership for at least six months,

[pytest-dev] Code of conduct issues

Hi all, As one of the Code of Conduct (CoC) committee members ( https://github.com/pytest-dev/pytest/blob/master/CODE_OF_CONDUCT.md ) I want to apologise for the poor handling of issues that have led Bruno, Anthony and Ronny to step back from the project. As a group we failed to act decisively

Re: [pytest-dev] Strike for the climate on 20th (Friday)

I reckon go for it! Can we put a banner on the Github repo somehow? See you in the streets  Brianna On Wed, 18 Sep 2019 at 19:57, Bruno Oliveira wrote: > Hi everyone, > > pytest, devpi and tox want to join the Digital Climate Strike which will > happen next Friday: > >

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

Hi, It looks like there are a few more repos that could be claimed as well: https://tidelift.com/lifter/search/pypi/pytest-xdist https://tidelift.com/lifter/search/pypi/pytest-cov https://tidelift.com/lifter/search/pypi/pluggy https://tidelift.com/lifter/search/pypi/py etc. cheers Brianna On

[pytest-dev] Hacktober coming up

Hi, I was reminded today that github's month long event encouraging people to submit PRs to open source projects will begin once again in a week or so. I am not sure how much increased activity was notice last year, but perhaps it would be prudent to do a bit of extra issue grooming if we can.

[pytest-dev] Fwd: [CodeTriage] Help triage pytest-dev/pytest

On the topic of issue triage, this is a service we could promote people to use. But I guess it's a question if the problem is more rate of new issues or old issues never getting closed. Brianna -- Forwarded message - From: CodeTriage Date: Sun, 9 Sep 2018 at 16:38 Subject:

Re: [pytest-dev] Hacktoberfest - Beginner Issues

Some projects have a bug triaging guide, eg http://docs.hood.ie/en/latest/developers/TRIAGING.html . Writing up the existing process (eg intention of existing labels) may help more people carry out bug triage. On Sun, 9 Sep 2018 at 16:43, Brianna Laugher wrote: > I have seen a lot of proje

Re: [pytest-dev] Hacktoberfest - Beginner Issues

I have seen a lot of projects use something like https://github.com/apps/stale to auto-close issues after a certain amount of time has passed without activity. On Fri, 7 Sep 2018 at 04:21, Bruno Oliveira wrote: > > On Thu, Sep 6, 2018 at 2:26 PM Maik Figura wrote: > >> Hey everyone, >> >> I

Re: [pytest-dev] Documentation proposal

Yes thanks Daniele! Daniele gave a great talk at PyCon Australia this past weekend about these four different types of documentation and how they are different/similar: https://www.youtube.com/watch?v=t4vKPhjcMZg=PLs4CJRBY5F1KsK4AbFaPsUT8X8iXc7X84=65 Daniele referred to "Brianna's tutorial",

[pytest-dev] Dependency CI

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/

Re: [pytest-dev] Postpone 3.0?

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"

Re: [pytest-dev] sprint logistics / food

Yes I am leaving Australia Saturday and would like to know soon that I have a bed somewhere. :) I'm not travelling directly to the sprints so I have some flexibility on when I arrive, but basically plan to arrive on the 19th. thanks! exciting!! :D Brianna On 7 June 2016 at 20:57, holger krekel

Re: [pytest-dev] planet pytest

Nice! Could someone add a link to the github repo/instructions about how to add a new feed, and maybe also an explicit link to the planet rss feed? Cheers Brianna On 12/04/2016 7:00 AM, "Bruno Oliveira" wrote: > Nice, subscribed! :) > > On Mon, Apr 11, 2016 at 5:51 PM

Re: [pytest-dev] Sprint participants writing a blog post?

Just sent out an update with a link to your post Andreas, thanks! Who's up next...Raphael? Floris? Florian? Holger? Are you all working on posts? :P cheers Brianna On 16 February 2016 at 22:24, Brianna Laugher <brianna.laug...@gmail.com> wrote: > That's a great post, I loo

Re: [pytest-dev] Sprint participants writing a blog post?

edback welcome: >>> > >>> http://blargon7.com/?p=204=1&_ppp=65d7c71c07 < >>> http://blargon7.com/?p=204=1&_ppp=65d7c71c07> < >>> http://blargon7.com/?p=204=1&_ppp=65d7c71c07 < >>> http://blargon7.com/?p=204=1&_ppp=6

[pytest-dev] Twitter update

Hi, I added Holger @hpk42 and Raphael @hackebrot to the pytestdotorg twitter account so they can tweet from it (via tweetdeck.twitter.com). If anyone else feels like they might be inspired to tweet on behalf of pytest, let me know offlist. cheers Brianna -- They've just been waiting in a

Re: [pytest-dev] RFC: pytest sprint indiegogo page (draft)

I think a dedicated page on the pytest site is a good idea (as well as a banner), then when it is over we can put the supporters names there (if they wish). 55 days is a long time, maybe a 30 day campaign is better? I would suggest to include even more context about what pytest is, maybe some

[pytest-dev] TLS certificate expired

Hi, It was pointed out on Twitter that our tls certificate has expired. Cheers Brianna ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest sprint 2016 / getting started

That's fine with me Raphael. BTW if anyone else would like to tweet for pytest, just contact me offlist to arrange :) I summarised the discussion etc so far here: https://github.com/pytest-dev/pytest/wiki/2016-dev-sprint and put some ideas I had about crowdfunding 'rewards'. I think more or less

Re: [pytest-dev] tentative pytest sprint june 2016 / funding

I guess more people might be able to commit to participating when event details are locked down. Bit of a catch 22 for organising. I don't have a preference on platform (I think kickstarter is best if making a lot of money/getting a lot of backers is the most important thing, which it's probably

Re: [pytest-dev] pytest sprint 2016 / getting started

I spoke to them and they seem positive about working something out, so I'm tentatively in :DDD On 8 January 2016 at 23:52, Brianna Laugher <brianna.laug...@gmail.com> wrote: > The dates are fine for me and I would love to come, but a bigger question > is if I can justify flying to

Re: [pytest-dev] pytest sprint 2016 / getting started

Bruno I see your 700€ and raise you 1000€... ;) The dates are fine for me and I would love to come, but a bigger question is if I can justify flying to Europe from Australia for such a short trip. I am starting a new job in February and should have enough leave for that, but not much more. I

Re: [pytest-dev] Paid contract desired/bountysource label on gh ?

I have never seen bounty stuff work well in open source TBH. Perhaps the website needs to be a bit more pointed in showing that there are consultants (such as Holger, but surely others too) available to work on pytest for a fee. IMO pytest is well into the size and popularity that it would

[pytest-dev] Europython sprints

Hi! I thought we could try and be a bit organised for the sprints, in terms of planning things to work on and who will be there and so on. So I made a wiki page: https://github.com/pytest-dev/pytest/wiki/Europython-2015-sprints Please add yourself if you'll be there, or add a task (or reply

[pytest-dev] adopt pytest month is over!

Hi all, So adopt pytest month is officially over! I am working on surveys for the helpers and projects and will send them out this week. I hope everyone enjoyed it and maybe even learned something. One thing, the helpers for Nefertari (REST API framework built on Pyramid and ElasticSearch) are a

Re: [pytest-dev] Let's have an Adopt pytest month

Hello all! We finally have a web page for adopt pytest month: http://pytest.org/latest/adopt.html If you would like to be a helper, please fill out this short form, preferably in the next week or so: http://goo.gl/forms/nxqAhqWt1P I will use the information to try and pair helpers with

[pytest-dev] Setting up tox

Hello, The contributing guide ( http://pytest.org/latest/contributing.html ) is still missing a couple of steps I'm afraid... I installed tox in my virtualenv and then ran python runtox.py -e py27,py33,flakes as advised. At the end of the run tox tells me: ERROR: py27: could not install deps

Re: [pytest-dev] Setting up tox

On 16 April 2014 16:44, holger krekel hol...@merlinux.eu wrote: I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) visible or available to this virtualenv. Any ideas? It should be on the PATH, so

Re: [pytest-dev] fixtures and pylint W0621

On 3 December 2013 18:39, holger krekel hol...@merlinux.eu wrote: Right, it seems that when we introduced @pytest.fixture we decided you can either use the prefix or the marker. That could be lifted but i wonder if we should rather go for a different convention because pytest_funcarg__ is not

Re: [pytest-dev] parametrize and ids

On 29 May 2013 17:48, holger krekel hol...@merlinux.eu wrote: agreed. One a sidenote, yesterday i introduced a briefer way to specify argument names. Your example would start like this: @pytest.mark.parametrize(wx,expectedCoverage,expectedTrend, ...) and you can also have spaces

Re: [pytest-dev] parametrize and ids

Another alternative - I would often prefer just doing what metafunc.addcall does if you don't specify an id, which is just make an integer, like so: Function 'test_filterPrecipOrTS[0]' Function 'test_filterPrecipOrTS[1]' Function 'test_filterPrecipOrTS[2]' Function

Re: [pytest-dev] Using a context manager in a funcarg/fixture

On 23 April 2013 17:33, Ronny Pfannschmidt ronny.pfannschm...@gmx.dewrote: Hi Holger, Brianna, there is https://github.com/pelme/**pytest-contextfixturehttps://github.com/pelme/pytest-contextfixture which seems to handle it for the time being Hi Ronny, I didn't know about that, but I

[pytest-dev] parametrize + xfail

Hi again :) A common problem I have is that I have a test that is parametrized with py.test.mark.parametrize, I discover a bug, I want to add another test case for that bug and mark it as xfail. I have done something based on