Mailman 3 December 2015 - pytest-dev

pytest-bdd 2.16.0 released
by Florian Bruhin Dec. 20, 2015

Dec. 20, 2015

Hey, I'm happy to announce I was added as a PyPI maintainer for pytest-bdd (thanks, Oleg!) and just released 2.16.0. This fixes deprecation warnings emitted by python 3.5 (because of inspect.getargspec) and pytest 2.8 (because of addhooks and __multicall__). It's still compatible with pytest 2.7 for now. Florian -- http://www.the-compiler.org | me(a)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/

1 0

State of pytest-bdd
by Florian Bruhin Dec. 16, 2015

Dec. 16, 2015

Hey, I'm quite a happy user of pytest-bdd[1], but it has some issues with deprecation warnings of Python[2] and pytest[3] which I fixed in the linked PRs. This was a month ago, unfortunately I still got zero reactions on those PRs... What can I do in such a case? It seems Anatoly Bubenkov isn't very active anymore on the plugin, and Oleg Pidsadnyi who has answered to some of the issues I opened seems very busy as well. I'd like to get that plugin in shape a bit more (e.g. by fixing those things and getting the tests/Travis to pass[4] again), but that'd mean I'd really like some more people (e.g. me :P) to be able to do releases on PyPI, and ideally have the OK of Anatoly/Oleg to actually do a release. Right now I could just merge my own PRs, but of course I'd prefer not doing that, and it doesn't help much without a release. Otherwise I'd have to fork the plugin as I'm a happy user of it other than those issues, and I'd really like to avoid that... Florian [1] https://github.com/pytest-dev/pytest-bdd [2] https://github.com/pytest-dev/pytest-bdd/pull/164 [3] https://github.com/pytest-dev/pytest-bdd/pull/163 [4] https://github.com/pytest-dev/pytest-bdd/issues/162 -- http://www.the-compiler.org | me(a)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/

3 2

pytest hangout meeting minutes
by Florian Bruhin Dec. 16, 2015

Dec. 16, 2015

We had an (experimental) Google Hangout meeting with some core developers today - here are the notes I took, completely unedited because I want to go to sleep ;) If I missed or misrepresented something, please let me know - sorry! pytest hangout meeting ====================== people ------ - Bruno/nicoddemus - Holger/hpk - Florian/The-Compiler - Floris/flub - abusalimov (pytest-catchlog contributor) - Ronny/ronny ronny: meta-organization ------------------------ ronny proposes to have a meta-organization to have an issue tracker and wiki to collect tasks/informations involving more than one pytest-dev project. Something similar to metaflask. Meta-things like how pytest-dev work, how to release those, etc. Also collect infos about the members of the project. -> Task workflow for management tasks which would feel clunky on a ML https://github.com/pocoo/metaflask Bruno sees some value as there's a plugin index thing there. flub asks if this isn't basically the same than using a prefix on PyPI. ronny/bruno: There's much more information than you could have on PyPI, you could add information like compatibility etc. flub: Let's try it - worried that it's another data source to get out of data ronny: We should re-evaluate it in 6-12 months and see how well it worked. hpk: plugincompat is already there and interesting - why not just add a 'people' page on the website? flo: I think having a machine-readable represenation of plugins and people doesn't make sense, even metaflask is a graveyard. flub: We already have an overview of recommended plugins in the docs, as for logging, just let's clarify there. ronny: but what about cross-project issues, I don't want those in the pytest tracker. e.g. a plugin moving to github. I'd like to see a separate bug tracker for ecosystem tasks. hpk: Why not just a 'cross' label for pytest issues. I don't think it's worth it to have a repo just for issue tracking? The issues also are more visibile like currently. flo: I don't see why pytest (as an ecosystem) is concerned about other projects moving. bruno: Other than movements, what do you think should be there? ronny: e.g. maintainer applications or moving to pytest-dev? hpk: I think that's fine on the mailinglist (flo points out it's documented that way already) ronny: okay, let's do labels for issues then and use the ML for other stuff. hpk: sprint ----------- What about a pytest sprint in spring and doing crowd-funding for travel? ronny: he'd like to ask one of the Plone maintainers who's interested in pytest and experienced in setting up those sprints. everyone likes the idea! ronny: moving other projects to github -------------------------------------- ronny is currently working on a better import from bitbucket to github. ronny would like to migrate stuff from bb to gh flub: the maintainer of that would definitely need to agree, ronny agrees. -> move every project where the maintainers agree to github ronny: automated releases ------------------------- ronny: pushing signed tag to github -> get release uploaded to PyPI hpk: that's the golden aim, but regendoc is still not completely automated. ronny: I want to work on that, with Travis creating a PR every time something changes via regendoc. florian/ronny: Only signed tags should cause releases! hpk: I'm still very sceptical about that - it often takes a couple of tries to release something. ronny: but you can create rc tags, etc. etc. until things look right. hpk: I like to create an artefact, test that, and release *exactly that*. With a tag workflow you lose that ability. ronny: But it would with reducable builds. The build system should create the same artefact. hpk: Let's do a PR against howtorelease. I want an automated process, I just don't think tagging is the right way to do that. -> The work is a good idea either way, no matter whether we trigger the process via tags or another mechanism. bruno: At work we create a release branch, that branch generates artefacts which aren't published yet. I can *manually* publish and tag it then. flo: I'd like it most if *testing* was automated. bruno: What about using devpi via travis? ronny: We could have a release branch and then make travis do something different there. general idea: PR -> release branch -> travis uploads a release somewhere and tests it -> you can publish that artifact holger: I'm doing releases for 7-8 projects - we do want to be sure wheels are working properly. wheels already were broken earlier. flub: But that works already with an option? I manually build with setup.py and use tox to test those? ==> we can all agree on automating steps and the general idea holger: other issues are the changelog or merging features/master. Usually when I merge something into master I merge it into features as well. holger: What about doing auto-merges via bot of master -> features flo: I think this is too noisy, what about weekly or so? holger: We don't really have a way to do this systematically so far. bruno: Why not just before every master/bugfix release? If we fix a bug we'll do a release anyways, so why not do it then? (holger leaves) ronny: subtests --------------- new concept introduced to unittest.py with py3 - you can have sub-tests which means the test still continues when an assertion fails. this would allow to create "sections" with proper names (and reporting) for larger tests. flub: So what's the challenge about that? [I couldn't really follow, so no logs here, sorry] ronny: capturing ---------------- ronny: We currently replace sys.std... objects and replace them by capturing ones. I'd like to add a kind of capturing where the capturing captures the whole test run. [I couldn't really follow, so no logs here, sorry] --> let's move it to the ML because it's better when written deferred until later -------------------- - unittests in pytest testsuite - DI framework - 3.x plans -- Florian -- http://www.the-compiler.org | me(a)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/

2 1

Unforseen delay wrt hangout, might not make it before 21:15
by Ronny Pfannschmidt Dec. 15, 2015

Dec. 15, 2015

Hi, As of now in the best case, I can still arrive home at 21:00 But please be prepared that I might be up to 15 minutes late. Sorry for the inconvenience. MFG Ronny

2 1

Parametrized scope question
by Alex Netes Dec. 15, 2015

Dec. 15, 2015

Hello guys, I'm new to Pytest and I encounter something I cannot explain. I'm trying to give fixture fixt_func() a parameter fixt_prm and expect the fixture to be called only once as it defined with 'class' scope, but the fixture is called twice as it ignores the scope. What am I missing? @pytest.fixture(scope='class') def fixt_func(request, resource, fixt_prm): print fixt_prm class TestA(): @pytest.mark.parametrize('resource', ['x'], scope='class') @pytest.mark.parametrize(fixt_prm ', ['x'], scope='class') @pytest.mark.parametrize('prm', ['a', 'b']) def test_a(self, prm, fixt_func) assert True

3 6

thanking for PRs?
by holger krekel Dec. 13, 2015

Dec. 13, 2015

I was wondering about the practise to have PR authors add themselves to AUTHORS and CHANGELOG. The latter particularly is a bit odd, i.e. to thank yourself for submitting a PR. What do you all think about having the merger do this last bit (changelog entry)? AUTHORS can also be usually obtained from the history so that contributors can concentrate on tests, code and possibly docs. my 2c, holger

5 5

Hangout Time Di 15.12.15 21:00
by Ronny Pfannschmidt Dec. 12, 2015

Dec. 12, 2015

Hi everyone, after Holger confirmed as maybe and Bruno confirmed the time in chat, the Hangout will be Di 15.12.15 21:00 best regards, Ronny

1 0

pytest 2.8.5 released
by Bruno Oliveira Dec. 12, 2015

Dec. 12, 2015

Hey, I'm happy to announce pytest 2.8.5 has been released. This release is supposed to be drop-in compatible to 2.8.4 pytest is a mature Python testing tool with more than a 1100 tests against itself, passing on many different interpreters and platforms. 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: Alex Gaynor aselus-hub Bruno Oliveira Ronny Pfannschmidt Happy testing, The py.test Development Team 2.8.5 (compared to 2.8.4) ------------------------- - fix #1243: fixed issue where class attributes injected during collection could break pytest. PR by Alexei Kozlenok, thanks Ronny Pfannschmidt and Bruno Oliveira for the review and help. - fix #1074: precompute junitxml chunks instead of storing the whole tree in objects Thanks Bruno Oliveira for the report and Ronny Pfannschmidt for the PR - fix #1238: fix ``pytest.deprecated_call()`` receiving multiple arguments (Regression introduced in 2.8.4). Thanks Alex Gaynor for the report and Bruno Oliveira for the PR.

1 0

[proposal] creation of a pytest-dev meta organisation on github
by Ronny Pfannschmidt Dec. 7, 2015

Dec. 7, 2015

Hi everyone, given that pytest-dev is slowly growing, i'm feeling it is necessary to have a transparent management channel to see and communicate the details that span more than one project, and their management that includes infrastructure, addition of projects, handling maintainer management as well as simpy stuff like the planned/ongoing github migration of further projects. an example of such a management channel that i liked was the meta-flask organisation that the pocoo team created around flask. for further effects it might make sense to think about something that works for tox/devpi/execnet as well -- Ronny

2 1

Doodle for a potential hangout call
by Ronny Pfannschmidt Dec. 7, 2015

Dec. 7, 2015

Hi Everyone, if possible i'd like to get a larger part of the pytest team into a hangout and concisely talk about a few topics around: * backward compat * pytest 3.0 and some feature ideas to be fleshed out specifically after the call * xdist * the kinda stagnated move of many more repos to github so i made a doodle http://doodle.com/poll/ez2898mrigfwe278 the time is in central europe and chosen to be late to ease getting bruno on board -- Ronny

1 0