Mailman 3 July 2018 - pytest-dev

Partnership possibility with Pytest
by Alex Georgie Aug. 8, 2018

Aug. 8, 2018

Hi everyone, I'm Alex from SeedAndDew. I was chatting with Holger and Bruno about SeedAndDew and whether Pytest would like to participate and they mentioned bringing it to the dev mailing list to get your opinions. *What is it?* SeedAndDew is a common subscription platform that allows users to contribute to a number of open source projects with a single subscription. The idea here is that it's a lot easier to get people to contribute $10/month to every open source project they work with than it is to get them to contribute $5/month for a specific project. The subscription revenue will be distributed based on the amount of time users spend reading documentation of the respective project which I anticipate will correspond well with actual use. So if a user spends 10% of their time reading the Pytest documentation, you get 10% of the subscription revenue. *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 seconds a user is on your site. If the user is part of our network, we would have provided a cookie to them when they signed in which gets passed to us when that call is made. We authenticate using that cookie and assign that drop to them and you. If they are not part of the network there is no cookie, they won't be authenticated and the process ends there. We aggregate those drops at the end of the month to figure out the revenue distribution. The info we have is purely opt in since the user need to not only have an account with us but pay us every month. We haven't built this yet, but the intention is to keep that data for 3 months for auditing purposes and then delete it. We take a 30% cut of the subscription that includes payment processing costs which allows us to be sustainable, so we don't need to get creative with the data. The other feature needed for GDPR is the export of user data which is also in the pipeline. Our goal is to increase the pool of people who contribute to open source by removing the friction of having to manage subscriptions paid to specific projects and changing it as your stack and interests change. This would be a passive income source that doesn't require any further work outside of the initial integration. So far we have 10 projects including SQL Alchemy, RSpec, Bundler, Browsh and Parse. Does this seem like something you would be interested in? Thanks, Alex <http://mailstat.us/tr/opt-out?guid=ycoxm178jk9b4dpm> <http://mailstat.us/tr/t/dummy>

5 7

Code of conduct for pytest organisation on GitHub
by Dave Hunt Aug. 4, 2018

Aug. 4, 2018

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 project does not currently have a code of conduct according to https://github.com/pytest-dev/pytest/community <https://github.com/pytest-dev/pytest/community>. Is there one documented elsewhere? If not, which should we adopt? Cheers, Dave

6 10

pytest 3.7.0 released!
by Bruno Oliveira July 31, 2018

July 31, 2018

The pytest team is proud to announce the 3.7.0 release! pytest is a mature Python testing tool with more than a 2000 tests against itself, passing on many different interpreters and platforms. The highlight of this release is support for package-scoped fixtures (still experimental). Please try it out and give us feedback! Changelog: http://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: * Alan * 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

2 1

command line options not working?
by Derek Sisson July 29, 2018

July 29, 2018

I've been using command line options for years, but they no longer work for me. I get the message "unrecognized arguments". As a sanity check, I used the example from the documentation on https://docs.pytest.org/en/latest/example/simple.html?highlight=addoption ~~~~~ import pytest def pytest_addoption(parser): parser.addoption( "--cmdopt", action="store", default="type1", help="my option: type1 or type2" ) @pytest.fixture def cmdopt(request): return request.config.getoption("--cmdopt") ~~~~~ (v3)$ pytest --cmdopt=type2 usage: pytest [options] [file_or_dir] [file_or_dir] [...] pytest: error: unrecognized arguments: --cmdopt=type2 inifile: None rootdir: /Users/derek/dev/example/example I'm using pytest-3.6.4 on OSX Sierra -- thanks, --derek

2 2

New plugin: pytest-lambda, or: lambda fixtures
by Zach Kanzler July 29, 2018

July 29, 2018

I've been developing some pytest idioms at work (startup), in an attempt to make it not just part of the process, or a disapproving look at code review, or a "*shrug* well, that's startup culture #yolo #youonlylaunchonce"... but as a feature scaffolding tool. I figure, if it can help develop features *quicker*, peoples will *want* to use it. Since you asked, of course I'll pause for a quick personal aside! Ya see, when I was growings up, my pa used to say "Zach, do whatever the hell you want, but only put on the credit card what you have in the bank." Working at a start-up, the pressure to fart out features sometimes makes skipping testing seem like it aligns with business goals. If my dad were here now, or understood anything about what I do for work, he'd slap their hands — "yeah, you can purchase the feature with your credit card, son, but you don't own it." Unlike regular debt, when technical debt piles up, and there's no time left in the day to work another job to pay it all off, there's no bankruptcy — there are only two options: forced labor, or DEATH! Anyway, I found with a more compact form of expression for test fixtures, I experimented more, and upon returning to those tests months later, I found I could skim through the code and grok it well. pytest-lambda <https://github.com/theY4Kman/pytest-lambda> offers `lambda_fixture`, which is essentially just `pytest.fixture` whose name is derived from the attribute it's assigned to. As well, for convenience, it also offers: - `static_fixture` — to return static value - `error_fixture` — to raise an exception - `not_implemented_fixture` — to raise a NotImplementedError, useful for abstract test mixins - `disabled_fixture` — to raise a HeyDontUseThisThingError (not really, but you get the idea), useful for failing early on known erroneous environments — 0xDEADBEEFing like the wholesome dev you are Also, I think this is my first message to the list, so, uh, hi, y'all! I'm Zach, I work for a cybersecurity startup. I fell in love with Python at an early age, embedding <https://github.com/theY4Kman/viper> it into Counter-Strike: Source 'cause I didn't want to use the C-like Pawn lang to write plugins. Years later, I discovered pytest and fell deeply in love. I gave a shot porting <https://github.com/theY4Kman/pysmx> the Pawn VM to Python, so people could test their plugins with pytest. One day I got my first tattoo, on the same day I got a Python tattoo, and can you believe it, on the same day I got my only tattoo. I'm occasionally long-winded, I think stuffy docs are unread docs, and it's a pleasure to meet y'all :) Cheers, Zach "theY4Kman" Kanzler

1 0

New plugin: pytest-steps
by Sylvain MARIE July 27, 2018

July 27, 2018

Dear pytest enthusiasts After a bit of hesitation I split my pytest-cases plugin in two independent packages * pytest-steps provides ways to break down a test into steps, with optional shared results and dependencies * pytest-cases provides ways to separate test functions from test cases data / generators https://smarie.github.io/python-pytest-cases/ https://smarie.github.io/python-pytest-steps/ Don’t hesitate to provide some feedback, whether positive or critical (as always -> issues page is open 😊 ) Kind regards Sylvain

1 0

Disable pushing directly to features and master branches
by Bruno Oliveira July 7, 2018

July 7, 2018

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 commit rights to the repository. To prevent changes to "master" and "features" branches to go unnoticed when the email service gets discontinued, I propose to disable direct pushes to those branches (using the GitHub option for that). Opinions? If nobody opposes I plan to enable this by the end of the day, as it is just a check box on GitHub's UI to revert this decision anyway. Cheers, Bruno.

6 6

[PROPOSAL] switchgin over from gitmate via pytestbot to gitmate as an github app
by RonnyPfannschmidt July 6, 2018

July 6, 2018

Hi everyone, im considering switching the pytest-dev repo to gitmate using the github gitmate app instead our bot account this would come with a set of additional permissions as far as i can tell and i' like to hear opinions from the others before proceeding -- Ronny

3 3

New pytest plugin: pytest-cases
by Sylvain MARIE July 5, 2018

July 5, 2018

Hello dear pytest community members A small email to share this new plugin with you: https://smarie.github.io/python-pytest-cases/ I wrote it for our internal data science production code tests, for which we often have dozens of datasets to throw on the same function. Don’t hesitate to let me know what you think (on the github/issues page directly for bugs and feature requests 😊) Kind regards -- Sylvain

2 2

pytest 3.6.3
by Bruno Oliveira July 4, 2018

July 4, 2018

pytest 3.6.3 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at http://doc.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * 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

1 0