Mailman 3 June 2015 - pytest-dev

Working with other dependency injection systems
by Kai Groner Sept. 10, 2015

Sept. 10, 2015

Hi testing people! I'm trying to figure out how I can test a code base that uses an existing dependency injection system. I've run into two problems, and I have solutions for each of them but I think maybe there is a better way, so I'm looking for some advice. The first problem is how do I override how a test using this injector is called? I think I want to use the pytest_runtest_call hook, but it still tries to invoke the test without the injector. My current solution is to use the experimental hookwrapper mechanism to replace item.obj with a partially bound version, then restore it afterward. The second problem I'm having is the py.test fixture system is trying to resolve arguments that are provided by this other injector. How can I tell it that some of these don't need to be provided? My current solution is to blind py.test with a wrapper function with a *a, **kw signature. I use functools.wraps, so annotations are introspectable for the other injector, and delete the __wrapped__ attribute to prevent py.test from introspecting it. Is there a nicer, and perhaps less blunt, way to influence the funcarg fixture behaviors? I've tried a couple things with the pytest_collection_modifyitems hook, but haven't gotten anything that works yet. Other details to know about this injection system: - we want to build and teardown the injector with each test - we may want to configure the injector differently for some tests (possibly with fixture data from py.test) Thanks, Kai

2 6

github push notification / pytest channel
by holger krekel July 4, 2015

July 4, 2015

Hey Bruno, all, i notice that we don't have push notifications to the #pylib channel. Could someone care for that? What's good practise for github there? With bitbucket we have a "trumpet" bot running on hq.merlinux.eu which could probably be configured to accept github notifications. FWIW the trumpet daemon is currently living under ronny's account on pytest.org. Besides, i am wondering if we should use a new #pytest channel instead of the #pylib one. "pylib" is not really a primary project anymore (py.test used to be part of pylib several years ago). I've registered #pytest on freenode and i can probably add others. best, holger -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu

3 5

moving to git / issues?
by holger krekel June 25, 2015

June 25, 2015

Hi all, i we want to move pytest to github what would we do with the issues? Can someone experiment with migrating the issues to a github repo (at some user location, not pytest-dev)? A quick search revealed https://github.com/vbabiy/bitbucket_issue_migration which might help. best, holger -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu

7 36

pytest-2.7.2: bug fixes
by holger krekel June 23, 2015

June 23, 2015

pytest-2.7.2: bug fixes ======================= pytest is a mature Python testing tool with more than a 1100 tests against itself, passing on many different interpreters and platforms. This release is supposed to be drop-in compatible to 2.7.1. See below for the changes and see docs at: http://pytest.org As usual, you can upgrade from pypi via:: pip install -U pytest Thanks to all who contributed to this release, among them: Bruno Oliveira Floris Bruynooghe Punyashloka Biswal Aron Curzon Benjamin Peterson Thomas De Schampheleire Edison Gustavo Muenz Holger Krekel Happy testing, The py.test Development Team 2.7.2 (compared to 2.7.1) ----------------------------- - fix issue767: pytest.raises value attribute does not contain the exception instance on Python 2.6. Thanks Eric Siegerman for providing the test case and Bruno Oliveira for PR. - Automatically create directory for junitxml and results log. Thanks Aron Curzon. - fix issue713: JUnit XML reports for doctest failures. Thanks Punyashloka Biswal. - fix issue735: assertion failures on debug versions of Python 3.4+ Thanks Benjamin Peterson. - fix issue114: skipif marker reports to internal skipping plugin; Thanks Floris Bruynooghe for reporting and Bruno Oliveira for the PR. - fix issue748: unittest.SkipTest reports to internal pytest unittest plugin. Thanks Thomas De Schampheleire for reporting and Bruno Oliveira for the PR. - fix issue718: failed to create representation of sets containing unsortable elements in python 2. Thanks Edison Gustavo Muenz - fix issue756, fix issue752 (and similar issues): depend on py-1.4.29 which has a refined algorithm for traceback generation. -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu

1 0

Re: [pytest-dev] github push notification / pytest channel
by Tom Viner June 23, 2015

June 23, 2015

+1 for Gitter. Really reduces the barrier to entry for people to engage.

5 4

Pytest migration to GitHub
by Bruno Oliveira June 23, 2015

June 23, 2015

Hi everyone, Today we will migrate the pytest repository from bitbucket (Hg) to GitHub (Git), sometime after 6pm (GMT -03:00). Until then feel free to commit and handle issues as usual, but when the process starts please refrain to make any changes to issues or new commits until the process finishes. I will send an email to this list when the process officially starts, and it is expected to take no longer than 1 hour before normal work, now on the new repository, can resume. For those interested, here are the steps for the migration: 1. Create github.com/pytest-dev/pytest and move current issues; 2. Convert pytest Hg repository to Git and upload to GitHub; 3. Add to bitbucket's README a notice about the move to GitHub, and that new issues/PRs should be posted there; (At this point, work on the new repository can resume) 4. Ask submitters to re-create PRs at the new repository; 5. Update all links in the documentation and PyPI; 6. Update "how to contribute" docs; 7. Upload new docs to pytest.org; 8. Send an email to all relevant mailing lists about the migration; Suggestions and comments are welcome! Cheers,

3 5

2.8.0 release plan? 2.7.2?
by Bruno Oliveira June 22, 2015

June 22, 2015

Hi, Do we have an idea of when we would like have a 2.8.0 release, or at least what we would like to see in the new version? And about 2.7.2? I see there are a couple of fixes that are in master but should be backported to pytest-2.7 branch before making a 2.7.2 release. Cheers,

5 8

Re: [pytest-dev] plugins/pytest-qt and cx_Freeze
by Laura Creighton June 18, 2015

June 18, 2015

cx_Freeze is buggy. I think you hit one. Laura

1 0

Re: [pytest-dev] 2.8.0 release plan? 2.7.2?
by Laura Creighton June 18, 2015

June 18, 2015

In a message of Thu, 18 Jun 2015 10:22:40 +0200, Tibor Arpas writes: >How about the new hook call system vs the old __multicall__ ? Is the plan >still to deprecate the old way in 2.8 and remove in 2.9? > >Any idea how many plugin-s use it and will brake (or were already updated)? > >Tibor > Eeeee. Can somebody point me at the new hook system. I have code I had no idea was in immenent threat of breakage .... Laura

2 1

Re: [pytest-dev] Trove Classifier for pytest plugins
by Laura Creighton June 18, 2015

June 18, 2015

In a message of Thu, 18 Jun 2015 04:03:05 -0000, Bruno Oliveira writes: >Hi, > >Recently Jason R. Coombs proposed to create an specific trove classifier >for pytest plugins: > >https://github.com/pytest-dev/plugincompat/issues/16 > >One benefit is that it would make it easier for people to find pytest >plugins, as the recommended approach of searching for "pytest-" named >packages leaves some of the existing plugins out. > >I like the idea, but would like to hear from the people here first. > I just discovered, grrr, half way through writing a plugin, that it already existed. I didn't even know about searching for pytest - and it wouldn̈́'t have found the one that I didn't need to write a second in any event. So I think this is a great idea. I see no downside at all. What would it be? Laura

2 1