Re: [pytest-dev] [proposal] introducing attrs to the codebase

Hi Ronny, Could you list the classes which you think would be changed to use 'attrs'? I'm not against adding another dependency if it can help us maintain the codebase. Also, introducing a new dependency should be done in `3.1.0`, not in a patch release. Cheers, Bruno. On Tue, Dec 6, 2016 at

[pytest-dev] pytest 3.0.5 released

Vojnovic * Bruno Oliveira * Daniel Hahler * Duncan Betts * Igor Starikov * Ismail * Luke Murphy * Ned Batchelder * Ronny Pfannschmidt * Sebastian Ramacher * nmundar Happy testing, The pytest Development Team ___ pytest-dev mailing list pytest-dev@python.org

Re: [pytest-dev] t-shirts and stickers now out, thanks Florian!

On Tue, Nov 29, 2016 at 3:14 AM Florian Bruhin <m...@the-compiler.org> wrote: > Hey, > > * Bruno Oliveira <nicodde...@gmail.com> [2016-11-28 19:39:51 +]: > > Just received mine, the shirt looks really cool! > > Glad to hear that! Makes me wonder where it was

Re: [pytest-dev] t-shirts and stickers now out, thanks Florian!

Hi everyone, Just received mine, the shirt looks really cool! Thanks Florian and Vasily! Cheers, On Thu, Oct 27, 2016 at 8:18 PM Oliver Bestwalter wrote: > Hi Florian, > > I really appreciate, that you opted for the harder but better quality > route. The quality is

Re: [pytest-dev] Session state

Hi Alexander, On Mon, Nov 14, 2016 at 9:34 PM Alexander Belopolsky < alexander.belopol...@gmail.com> wrote: > where runtestprotocol() is a function returning a list to reports, but > this list is apparently discarded by the runner. Can someone explain how > reports are passed from the runner

Re: [pytest-dev] Commit access to pytest

Hi everyone, I like the idea as well. As Floris mentioned, giving people commit access is certainly a good way of motivating new contributors. Anyone up for writing up those guidelines so we can review them and decide if we want to move in that direction or not? Cheers On Mon, Nov 14, 2016 at

[pytest-dev] pytest 3.0.4 released

who contributed to this release, among them: * Bruno Oliveira * Dan Wandschneider * Florian Bruhin * Georgy Dyuldin * Grigorii Eremeev * Jason R. Coombs * Manuel Jacob * Mathieu Clabaut * Michael Seifert * Nikolaus Rath * Ronny Pfannschmidt * Tom V Happy testing, The pytest Development Team

Re: [pytest-dev] showing reason for skipped and verbose

Hi James, I guess this makes sense. Could please report an issue in the bug tracker: https://github.com/pytest-dev/pytest/issues? Thanks, Bruno. On Fri, Nov 4, 2016 at 11:04 AM James wrote: > $ py.test -v testscript.py > = test session starts >

Re: [pytest-dev] Moving pytest-rerunfailures to pytest-dev

group. > * Add Michael Howitz (icemac at GitHub) to the pytest-dev team and the > pytest-rerunfailures-developers group. > > Thanks a lot! > > Am 03.02.2016 um 16:03 schrieb Bruno Oliveira <nicodde...@gmail.com>: > > On Wed, Feb 3, 2016 at 5:15 AM Florian Bruhin <m.

Re: [pytest-dev] t-shirts and stickers now out, thanks Florian!

Hi Ronny, On Tue, Oct 25, 2016 at 11:15 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > b) sovereign build/ci infrastructure for both pytest* and tox* > (**i** feel that travis are very limiting and actively > prevent doing certain kinds of automation in a simple

Re: [pytest-dev] T-Shirt has arrived!

Pics or didn't happen! :) Still waiting for mine. ^^ On Mon, Oct 24, 2016 at 3:04 PM Omar Kohl wrote: > Hey, > > the 2016 Sprint T-Shirt arrived today! Thanks a lot, very cool :-) > > Omar > ___ > pytest-dev mailing list >

Re: [pytest-dev] Proposal: python namespacign for markings/marker objects

Hey Ronny, On Wed, Sep 7, 2016 at 10:45 AM Ronny Pfannschmidt wrote: > such a flat namespace really doesn't scale > > as such i would like to propose having marker types and objects as > importable objects > I'm not against adding support for it, but I wouldn't change it

Re: [pytest-dev] creating pytest-boxed and removing boxed from xdist

On Tue, Oct 11, 2016 at 7:46 PM oliver wrote: > Is there any plan to port boxed and xdist plugins to Windows? What are the > issues that have prevented implementation from happening (or happening > sooner, if planned)? > Hey, The boxed implementation depends on

Re: [pytest-dev] How to repeat tests with a setup-action before each repitition

Hello Emil, On Fri, Sep 30, 2016 at 6:26 PM Emil Petersen emil.peter...@thalmic.com wrote: I am looking to repeat some of the tests in my test suite, and want to call a certain action before each repetition. To be clear, I want to: 1) First, run all the

[pytest-dev] pytest 3.0.3 released!

. Thanks to all who contributed to this release, among them: * Bruno Oliveira * Florian Bruhin * Floris Bruynooghe * Huayi Zhang * Lev Maximov * Raquel Alegre * Ronny Pfannschmidt * Roy Williams * Tyler Goodlet * mbyt Happy testing, The pytest Development Team

Re: [pytest-dev] the sorry state of pylib tests and pylib

On Tue, Sep 27, 2016 at 11:14 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > > > On 27.09.2016 15:59, Bruno Oliveira wrote: > > On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt < > opensou...@ronnypfannschmidt.de> wrote: > >> as th

Re: [pytest-dev] the sorry state of pylib tests and pylib

On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > as things stand we have to maintain it until py.test no longer depends on > it > > a 2.0 release that kills py.code is a non-option as any project dependign > on ot will be limited in py.test version >

Re: [pytest-dev] the sorry state of pylib tests and pylib

Hi Ronny, How long do we plan to maintain pylib? Perhaps we can get rid of stuff we no longer wish to maintain (svn, py.code) and release a 2.0 version? If someone still needs that functionality, they can pin it. Not sure about the py.path encoding errors you mention though. Cheers, On Thu,

[pytest-dev] pytest-warnings in 3.1

Hi everyone, During the sprint Florian Schulze developed pytest-warnings[1], and later we decided to merge that into pytest 3.1. I was trying to remember: did anybody volunteer to do that? Cheers, [1] https://github.com/fschulze/pytest-warnings ___

Re: [pytest-dev] the move of pylib to github is technically finished

Well done ronny! :) On Sat, Sep 17, 2016, 05:10 Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi all, > > > i finished the move to github and did a few simple fixups > in the process i learned various details, and fixed bugs in the > migration tool > > now i feel confident i can

Re: [pytest-dev] transfer repo / pypi access / ML announce

On Wed, Sep 14, 2016 at 8:58 AM holger krekel wrote: > I am a bit concerned that people who transfer repos to pytest-dev think > that it receives magic maintenance because this relevant section in the docs > > >

Re: [pytest-dev] Move pytest-flask plugin to pytest-dev

I think the move is complete, let me know if you have any problems. Cheers, On Wed, Sep 14, 2016 at 8:13 AM Bruno Oliveira <nicodde...@gmail.com> wrote: > Vital, > > The steps are detailed here: > > > https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#subm

Re: [pytest-dev] Move pytest-flask plugin to pytest-dev

dze...@gmail.com> wrote: > I prefer to keep plugin under pytest-dev for consistency with > pytest-django. > > On Tue, Sep 13, 2016 at 7:26 PM Bruno Oliveira <nicodde...@gmail.com> > wrote: > >> Hi, >> >> I'm certainly fine with it as well. Let's just wait for

Re: [pytest-dev] pluggy moved to pytest-dev

Nice! Holger, is it OK with you if someone with push access to PyPI publish 0.4 soonish? This is required by https://github.com/pytest-dev/pytest/issues/1637 Cheers, Bruno. On Mon, Sep 12, 2016 at 5:59 AM holger krekel wrote: > > Ronny asked me to move the pluggy

Re: [pytest-dev] [wishlist] handling reuse of pytest plugins outside of pytest

Hey Ronny, Can you provide some examples of what you would like to accomplish? At least to me your email is a little vague and I wouldn't know where to start discussion about it... On Wed, Sep 7, 2016 at 10:47 AM Ronny Pfannschmidt wrote: > Hi, > > recently i am starting

Re: [pytest-dev] [proposal] regendoc automation via travis + pytest-bot on GH

Hi Ronny, To me it sounds great if we could automate regendoc. As we discussed online, the approach you propose sounds good as well. Are you planning to tackle this anytime soon? Cheers, Bruno On Wed, Sep 7, 2016 at 8:33 AM Ronny Pfannschmidt wrote: > hi, > > i would like

Re: [pytest-dev] [proposal] deprecating the pytest_namespace hook

On Fri, Aug 26, 2016 at 9:54 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > the problem it creates is, that we need to load plugins before even > parsing the config and before even having config object just in order to > literally monkeypatch a module > You mean that just

[pytest-dev] 3.0.1 tonight?

Hi everyone, Since 3.0.0 was released, two regressions have been reported and this afternoon the fix for the last one was merged. Unless someone still has some issue that they would like to work on for this release, I was thinking of making a 3.0.1 release tonight. What you guys think? Should we

Re: [pytest-dev] pytest 3.0.0 released!

On Fri, Aug 19, 2016 at 6:24 PM Bruno Oliveira <nicodde...@gmail.com> wrote: > This release contains a lot of bugs and improvements, and ... > Of course I meant "lot of bug *fixes*", sorry for the typo. :) Cheers, Bruno. ___ p

[pytest-dev] pytest 3.0.0 pre-release

Hello everyone, The pytest team has generated a 3.0.0 release candidate and would like to ask users to test the new package with their test suites. The package can be installed with: pip install -U -i https://devpi.net/nicoddemus/dev pytest Please report any serious regression on the issue

Re: [pytest-dev] Release candidate soon(tm)?

On Wed, Aug 17, 2016 at 2:17 AM Florian Schulze <florian.schu...@gmx.net> wrote: > Is it possible to preview the blog post somewhere? > I'm not sure, but you can clone it and preview it locally. Cheers, Bruno. > On 17.08.2016, at 02:52, Bruno Oliveira <nicodde...@gmail.

[pytest-dev] Remove invocation fixtures from 3.0?

Hi everyone, I've worked on the weekend on the issue discovered by Florian on the qutebrowser test suite, and unfortunately I think the current implementation will have to be re-thought because it contains a serious problem regarding finalizers when fixtures are being overwritten. Because

Re: [pytest-dev] pytest and Mozilla's Open Source Support program

On Mon, Aug 8, 2016 at 7:13 AM Florian Bruhin wrote: > Hey, > > via [1] (German) I just stumbled upon Mozilla's MOSS program[2]. > > They have a track[3] where they found generic OSS projects furthering > their mission, and another one[4] (probably more relevant to us)

Re: [pytest-dev] 3.0 next week?

On Fri, Aug 5, 2016 at 9:27 AM Florian Bruhin wrote: > I just tried the current features branch with the qutebrowser > testsuite, and noticed various things, roughly ordered by importance: > > - I get a RecursionError in pluggy during teardown of one of my > fixtures:

[pytest-dev] 3.0 next week?

Hi everyone, Is everyone OK with releasing pytest 3.0 next week? My idea is to: 1) Early in the week, create and publish a pytest-3.0 package on my devpi channel [1] and ask people to test it on twitter and the relevant mailing lists; 2) If there are no blocking issues reported, release it to

Re: [pytest-dev] can we remove the deprecated pytest.config variable assignment before 3.0

On Thu, Jul 21, 2016 at 2:29 AM Ronny Pfannschmidt 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

Re: [pytest-dev] can we remove the deprecated pytest.config variable assignment before 3.0

On Wed, Jul 20, 2016 at 6:31 PM Floris Bruynooghe f...@devork.be <http://mailto:f...@devork.be> wrote: On 20 July 2016 at 21:50, holger krekel <hol...@merlinux.eu> wrote: > > On Wed, Jul 20, 2016 at 16:15 +0000, Bruno Oliveira wrote: > >> Hi Ronny, > >&

Re: [pytest-dev] EuroPython Talk on pytest 3.0

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 wrote: > Hi, > > let's keep the #dropthedot in mind for the release that's really funny :D > > @Florian - sorry I can't

Re: [pytest-dev] Postpone 3.0?

On Thu, Jul 14, 2016 at 7:52 PM Raphael Pierzina 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

Re: [pytest-dev] Postpone 3.0?

Hi Raphael, On Thu, Jul 14, 2016 at 7:20 PM Raphael Pierzina 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 >

Re: [pytest-dev] EuroPython Talk on pytest 3.0

Hahaha I laughed over here! On Fri, Jul 8, 2016 at 6:20 PM 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

Re: [pytest-dev] EuroPython Talk on pytest 3.0

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

Re: [pytest-dev] pytest.readthedocs.io pointing to "latest"

On Fri, Jul 8, 2016 at 4:38 AM holger krekel 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. :)

Re: [pytest-dev] pytest 3.0 release check list

Thanks Oliver, nice work! I updated some of the issues as already done, plus added a few more. Could everybody who participated on the sprint also review, and add yourself if you plan to work on a task? Cheers, Bruno, On Wed, Jun 29, 2016 at 2:16 PM Oliver Bestwalter

Re: [pytest-dev] readthedocs building?

Hey Brianna, Here’s the docs on how readthedocs treats versions: http://docs.readthedocs.io/en/latest/versions.html So I changed *Default Branch* to *master* (this will point to latest) and *Default Version* to stable, which should be the last tag. In summary: - latest -> master - stable

Re: [pytest-dev] Testing of console scripts

Hi Vasily, On Sun, Jun 12, 2016 at 3:24 PM Vasily Kuznetsov wrote: > > It took a while but today I finally finished the README and I think it's > sort of ready for someone to take a look: > https://github.com/kvas-it/pytest-console-scripts. The tests fail for > Python 2 on

Re: [pytest-dev] sprint logistics / food

Hey, On Tue, Jun 7, 2016 at 7:57 AM holger krekel wrote: > If anyone has any other questions, please post them here. > This just occurred to me, will we get whiteboard(s) and markers available at the sprint venue? I'm sure it would be useful for all kinds of discussion

Re: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs?

On Thu, Jun 2, 2016 at 10:22 AM Dave Hunt wrote: > > On 2 Jun 2016, at 13:13, Vasily Kuznetsov wrote: > > "1337 passed in 0.42 seconds" > > > <3 this > Hehehe, also liked this one (although "asserts before reverts" is also neat) Thanks, >

Re: [pytest-dev] pytest pre-sprint

On Wed, Jun 1, 2016 at 8:33 AM Steffen Allner wrote: > > If it does not fit to the schedule in advance and as we are some number > of people with less experience to pytest, it is maybe even usefull if we > do something on the first day with the interested part of the >

Re: [pytest-dev] Joining the sprint

Hi Stefan, Are you talking about a specific issue, or in a more general way? We have a list of general topics on the indiegogo page: https://www.indiegogo.com/projects/python-testing-sprint-mid-2016 This list could be used as a basis to search issues to work on. Cheers, Bruno On Thu, May 19,

Re: [pytest-dev] Running each test in a Vagrant VM?

Hi Chris, On Fri, May 13, 2016 at 2:35 PM Chris Spencer wrote: > How do you configure Pytest to create a new Vagrant VM before each test > and destroy it afterwards? > I've not done something similar myself, but I would implement this feature as a fixture, which would

Re: [pytest-dev] Testing of console scripts

On Thu, Apr 28, 2016 at 5:45 PM Vasily Kuznetsov wrote: > Yeah, this is exactly what I had in mind (articulated in more detail than > I had in mind :). > I think I'll put some code together when I have a bit of time and then we > can see. > Nice! Make sure to use

Re: [pytest-dev] Testing of console scripts

On Thu, Apr 28, 2016 at 1:20 PM Vasily Kuznetsov wrote: > Yes, exactly, I want to do both (in-process and subprocess). So while I'm > hacking on the new features I'd run in-process for speed and then I'd use > something like tox to run proper subprocess tests in different >

Re: [pytest-dev] Timing tests and fixtures

On Thu, Apr 28, 2016 at 7:57 AM Florian Schulze wrote: > Is there a plugin to measure the execution time of tests and fixtures > and the usage count of fixtures? > Hi Florian, I don't know about fixtures, but the --durations=N option will show the slowest N tests (0

Re: [pytest-dev] pytest overall execution timeout option

On Wed, Apr 20, 2016 at 1:30 PM Floris Bruynooghe wrote: > With the signal method (default if you're on unix) it raises an > pytest.fail.Exception from inside the signal handler, which means it > gets raised from inside the test function call, the test fails and > then finalizers

Re: [pytest-dev] pytest overall execution timeout option

On Wed, Apr 20, 2016 at 11:01 AM Shankar Hiremath < shankarhiremath2...@gmail.com> wrote: > As part of “pytest_sessionfinish” we are doing few major activities > (collecting cluster logs, artifacts, screen shots & videos of testing and > moving to central location), > so if kill the pytest based

Re: [pytest-dev] pytest overall execution timeout option

On Wed, Apr 20, 2016 at 10:38 AM Obermann, Stephan < stephan.oberm...@dolby.com> wrote: > Just a thought, but if you want to kill the whole test run after 2h no > matter what the actual test results are - why not simply set a timeout in > your test automation system (the one that calls py.test).

Re: [pytest-dev] Test discovery by subclassing

On Tue, Apr 19, 2016 at 8:34 AM Ronny Pfannschmidt wrote: > my understanding is, that the pytest_pycollect_makeitem > > hook is the official way to do something like that in plain

Re: [pytest-dev] Test discovery by subclassing

Hi Dave, Using plain pytest that is currently not possible, and I’m not aware of any plugin which allows this. You can implement your own collection rules by implementing the pytest_pycollect_makeitem

Re: [pytest-dev] pytest overall execution timeout option

On Mon, Apr 18, 2016 at 10:47 AM Ronny Pfannschmidt < i...@ronnypfannschmidt.de> wrote: > the given simple implementation is called at the setup of a test item and > has effect after teardown of that test item > > (note how py.test took 1.69 seconds, even tho the timeout is 1 second and > each

Re: [pytest-dev] pytest overall execution timeout option

Hi Shankar, I don’t know of any plugin that does this out of the box, but the simplest way I found is to implement this is using an auto-use fixture: # contents of conftest.pyimport pytestimport time def pytest_sessionstart(session): session.start_time = time.time()

Re: [pytest-dev] submitting nose2pytest for inclusion in pytest

On Wed, Apr 13, 2016 at 6:48 PM oliver wrote: > Thank you both, so based on the docs I can proceed to the next step (pull > request I think), let me know if I got this wrong. Cheers, > No problem! I created the teams on pytest-dev already, you should receive an

Re: [pytest-dev] planet pytest

Nice, subscribed! :) On Mon, Apr 11, 2016 at 5:51 PM Raphael Pierzina wrote: > Now pytest-tricks does have a feed > https://github.com/fschulze/planet.pytest.org/pull/4 :D > > On 11 Apr 2016, at 17:25, Florian Schulze wrote: > > > > On 11 Apr

[pytest-dev] New Trove Classifier: "Framework :: Pytest"

Hi all, A new Trove Classifier "Framework :: Pytest" has been added to PyPI[1] following a request I made some time ago[2]. With this users have another way to search for pytest plugins besides searching only for projects with "pytest-" prefix, which is great! Later on today I will update the

[pytest-dev] Pytest 2.9.1 released

contributed to this release, among them: Bruno Oliveira Daniel Hahler Dmitry Malinovsky Florian Bruhin Floris Bruynooghe Matt Bachmann Ronny Pfannschmidt TomV Vladimir Bolshakov Zearin palaviv Happy testing, The py.test Development Team 2.9.1 (compared

[pytest-dev] Pytest 2.9.0 released

Bruno Oliveira Buck Golemon David Vierra Florian Bruhin Galaczi Endre Georgy Dyuldin Lukas Bednar

Re: [pytest-dev] question about pytest_addoption

On Tue, Mar 1, 2016 at 10:30 AM Bryan Berry wrote: > Hi Bruno, I already successfully use that approach from one fixtures > package. However, I want to add command-line options from one or more > fixtures packages. Say i use ProductAFixture library that adds a >

Re: [pytest-dev] question about pytest_addoption

Hi Bryan, On Sun, Feb 28, 2016 at 4:21 PM Bryan Berry wrote: > A specific fixture library, say foo_fixture that handles the installation > of some particularly hairy proprietary software, may want to add additional > custom options. Perhaps, we need to pass this fixture a

Re: [pytest-dev] pytest 2.9.0-rc.1

On Fri, Feb 26, 2016 at 3:09 PM Florian Bruhin <m...@the-compiler.org> wrote: > * Bruno Oliveira <nicodde...@gmail.com> [2016-02-25 23:35:26 +]: > > On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin <m...@the-compiler.org> > wrote: > > > > &g

Re: [pytest-dev] pytest 2.9.0-rc.1

Hey Florian, Thanks for taking the time to try it out. On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin wrote: > Other than pytest-hypothesis breaking because it doesn't expect the > dash in the version number, That's strange, as having that dash is correct for

[pytest-dev] pytest 2.9.0-rc.1

Hi all, We released pytest 2.9.0-rc.1, a release candidate to try to identify any regressions before the official 2.9.0 release. It would be really helpful if people could install this version, execute their test suites and report any regressions to pytest-dev@python.org or the issues page[1].

Re: [pytest-dev] Make a 2.9.0-rc.1 release?

Hi Holger, On Sun, Feb 21, 2016 at 4:10 AM holger krekel wrote: > My experiences with beta/rc releases so far was that very few people go for > it. Doing a 2.9.0 and being prepared to fix regressions quickly might be > a path involving less efforts with a good result. YMMV.

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

On Sat, Feb 20, 2016 at 9:16 PM Tom Viner wrote: > Date: Sat, 20 Feb 2016 22:41:50 +1100 >> From: Brianna Laugher > > >> >> Who's up next...Raphael? Floris? Florian? Holger? Are you all working on >> posts? :P >> > > Me! :-) Here's a draft post

Re: [pytest-dev] GitHub Issues and Pull Requests templates

On Thu, Feb 18, 2016 at 11:05 AM Florian Bruhin wrote: > FWIW, another solution would be to add some empty lines and tell > people to pick a random non-empty line: > > >

[pytest-dev] GitHub Issues and Pull Requests templates

Guys, GitHub just announced support for Issues and PR templates[1]. I think this is even better than updating our CONTRIBUTING[2] file, so I was thinking of adding those for pytest. For issues: * include a good description * include py.test, operating system versions * pip list of the venv used

Re: [pytest-dev] How to add delay before processing captured output

Hi Nokolaus, On Wed, Feb 17, 2016 at 7:07 PM Nikolaus Rath wrote: > Is there a way to add a delay that is (1) only incurred when a test > fails and (2) executed right after the test fails (ie., before the capfd > finalizer runs)? > One way to execute something right after

Re: [pytest-dev] Announce pytest-wish a local search engine for code

On Sun, Feb 14, 2016 at 1:23 PM Alessandro Amici wrote: > Hello everybody out there using pytest, > > last year a colleague of mine and I came up with the idea of using tests > for searching code that implements a particular feature. > > As I didn't find anything similar on

Re: [pytest-dev] release process feature/master merge

On Sat, Feb 13, 2016 at 3:54 PM holger krekel wrote: > can you do the latter really? You'd have to transfer all html files > because they have the generated link at the top of each page. > > Seems easier to transfer current master's _template/* and annouce/* onto > the >

Re: [pytest-dev] Redirect pytest.org over readthedocs

On Sat, Feb 13, 2016 at 4:07 PM holger krekel wrote: > Let's move back quickly, though, if there are any problems. > So far i have not heart many complaints about pytest.org not working apart > from the recent ssl hickup which should be automated now with letsencrypt. >

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

On Sat, Feb 13, 2016 at 2:06 AM Brianna Laugher wrote: > Your writing is great Bruno! If you wanted I would be happy to edit a > draft though. > > On 12 February 2016 at 09:02, Holger Krekel wrote: > >> Your written English is pretty good so you

[pytest-dev] Visibility of project members

Hi all, I was browsing the peoples page at https://github.com/orgs/pytest-dev/people and noticed that most members have their membership set as "private". I believe most people left that setting as private because it is the default. You can easily see your setting to members outside the

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

Hi Holger, TBH I'm a little shy of my english speaking skills, so I rather don't do the interview. :S Someone else might be more suited! On Thu, Feb 11, 2016 at 7:10 AM holger krekel wrote: > > Hey Bruno, > > what about you? You have been incredibly active and it'd be

Re: [pytest-dev] pytest-sugar: tests skipped with pytest.mark.skipif not shown as such

Hi Thomas, It seems to be a bug in pytest-sugar. Could you please create a new issue in their issue tracker[1]? [1] https://github.com/Frozenball/pytest-sugar/issues Cheers, Bruno. On Sat, Feb 6, 2016 at 7:10 AM Thomas De Schampheleire < patrickdeping...@gmail.com> wrote: > Hi, > > (I asked

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

On Thu, Feb 4, 2016 at 8:14 AM holger krekel wrote: > > Totally agree. I configured it as flexible funding almost from the > beginning. > If you look at the campaign as an editor can you see that? > What makes you and others believe it is fixed funding? > Oh I was looking

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

Hi all, Sorry for chipping in so late, I didn't have a chance of looking more carefully at the draft until now. I think it looks great so far, and I like most of the suggestions given by others. I would like to stress on the part about it being flexible funding though, as I think this sprint

Re: [pytest-dev] Moving pytest-rerunfailures to pytest-dev

On Wed, Feb 3, 2016 at 5:15 AM Florian Bruhin wrote: > - Every project has a pytest-xyz-admin team, with its projects admins > in it, having admin permissions on the repo. > > This was already present, I now also added it as a repo admin team, > so you should have

Re: [pytest-dev] Moving pytest-rerunfailures to pytest-dev

Ahh cool, thanks for the research Florian. I think we should follow that procedure from now on. :) []s, On Tue, Feb 2, 2016 at 12:47 PM Florian Bruhin wrote: > * Floris Bruynooghe [2016-02-02 14:43:00 > +]: > > BTW, a more general

Re: [pytest-dev] pytest docs on readthedocs?

e server to use a 301 redirect response when accessing the old location? Cheers, Bruno. > > > Floris > > On 26 January 2016 at 01:42, Bruno Oliveira <nicodde...@gmail.com> wrote: > > Hi > > > > On Mon, Jan 25, 2016 at 12:39 PM Bruno Oliveira <nicodde..

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 12:42 PM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Am 25.01.2016 um 15:04 schrieb Florian Bruhin: > > * Ronny Pfannschmidt [2016-01-25 > 14:36:12 +0100]: > >> to that effect it might even be sensible to change from

Re: [pytest-dev] pytest docs on readthedocs?

On Mon, Jan 25, 2016 at 12:18 PM Floris Bruynooghe wrote: > > I think the latter is certainly possible, since that's what fabric does: > > > > http://www.fabfile.org/ > > http://docs.fabfile.org/en/1.10/ > > +1 to this layout > I will study how to use this later Today. On a

Re: [pytest-dev] a potential alternative to the py.code merge

On Mon, Jan 25, 2016 at 12:59 PM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > i have ideas for replacing/changing it in the back of my head since a > while now, > so i'd like to have a reasonable/easy testbed > > also we could avoid the need for api compatibility even if we copy

Re: [pytest-dev] Introduction

Hi Isaul! On Mon, Jan 25, 2016 at 5:42 PM Isaul Vargas wrote: > Hi everyone! My name is Isaul Vargas and I work as a software tester. > I have been using py.test since 2013 and I really like the fixture > interface of > Py.test it's a powerful abstraction! > ... > So, I've

Re: [pytest-dev] pytest docs on readthedocs?

On Mon, Jan 25, 2016 at 8:38 AM holger krekel wrote: > Hi Bruno, all, > > could you give me your handles on readthedocs so i can add you as > maintainers > to pytest.readthedocs.org? > Mine is nicoddemus. > > If we can maintain the current URL layout of pytest.org and have

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 9:06 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > I agree on the link article as well and like the model, > i propose a time-frame of either 3 or 4 months for the feature releases. > > My personal preference is 3 months. > I think that sounds good for

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 10:00 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > For bugfix releases i would like to do them as soon as possible > (i.e. try to stay within one day of the merge) > Hmmm what do you mean Ronny? A release after each bug fix is merged in? that would

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 9:49 AM Florian Bruhin <m...@the-compiler.org> wrote: > * Bruno Oliveira <nicodde...@gmail.com> [2016-01-25 11:43:27 +]: > > I think that sounds good for the feature releases. For bug fix releases I > > think a shorter time frame makes mo

Re: [pytest-dev] Configurable collection roots and reusable testsuites - Brainstorming

Hi Ronny, About reusable test suites, what I have done is to put the required tests/checks into fixtures or even classes which are importable across projects and reused there. Could you provide a more specific example of the problem you see? About the collection roots, I also didn't quite get

Re: [pytest-dev] how about merging features into master and a 2.9 release?

Hi Ronny, Sounds good too me. We've put off 2.9 for some time now. Let's start planning 2.9 two weeks for now then, to see if any critical bug which warrants a 2.8.7 release shows up. As an aside, I would like to see #1199 [1] in 2.9 as it will open up the path to solve a number of bugs

[pytest-dev] pytest docs on readthedocs?

Hi everyone, Currently one of the steps involved in the release process is manually generating the documentation and uploading to pytest.org (using rsync). I was wondering if we should move pytest docs over to readthedocs.org? It automatically builds and hosts the documentation based on tags or

[pytest-dev] pytest 2.8.6 released

of a ``monkeypatch`` call raises an ``ImportError``. - fix #1292: monkeypatch calls (setattr, setenv, etc.) are now O(1). Thanks David R. MacIver for the report and Bruno Oliveira for the PR. - fix #1223: captured stdout and stderr are now properly displayed before entering pdb when ``--pdb

<    1   2   3   4   5   >