From opensource at ronnypfannschmidt.de Sun Jul 1 08:24:39 2018 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Sun, 1 Jul 2018 14:24:39 +0200 Subject: [pytest-dev] [PROPOSAL] switchgin over from gitmate via pytestbot to gitmate as an github app Message-ID: 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 From nicoddemus at gmail.com Wed Jul 4 17:47:05 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 4 Jul 2018 18:47:05 -0300 Subject: [pytest-dev] pytest 3.6.3 Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvain.marie at schneider-electric.com Thu Jul 5 14:32:54 2018 From: sylvain.marie at schneider-electric.com (Sylvain MARIE) Date: Thu, 5 Jul 2018 18:32:54 +0000 Subject: [pytest-dev] New pytest plugin: pytest-cases Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Thu Jul 5 17:22:53 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 5 Jul 2018 18:22:53 -0300 Subject: [pytest-dev] New pytest plugin: pytest-cases In-Reply-To: References: Message-ID: Hi Sylvain, Interesting plugin, I like the idea of lazy data generation for parametrize! Thanks for sharing on the list. Cheers, Bruno. On Thu, Jul 5, 2018 at 3:33 PM Sylvain MARIE < sylvain.marie at schneider-electric.com> wrote: > 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 > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvain.marie at schneider-electric.com Thu Jul 5 17:42:56 2018 From: sylvain.marie at schneider-electric.com (Sylvain MARIE) Date: Thu, 5 Jul 2018 21:42:56 +0000 Subject: [pytest-dev] New pytest plugin: pytest-cases In-Reply-To: References: Message-ID: Thanks for your support Bruno ! Sylvain De : Bruno Oliveira [mailto:nicoddemus at gmail.com] Envoy? : jeudi 5 juillet 2018 23:23 ? : Sylvain MARIE Cc : pytest-dev at python.org Objet : Re: [pytest-dev] New pytest plugin: pytest-cases Hi Sylvain, Interesting plugin, I like the idea of lazy data generation for parametrize! Thanks for sharing on the list. Cheers, Bruno. On Thu, Jul 5, 2018 at 3:33 PM Sylvain MARIE > wrote: 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 _______________________________________________ pytest-dev mailing list pytest-dev at python.org https://mail.python.org/mailman/listinfo/pytest-dev ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. ______________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jul 6 11:13:12 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 6 Jul 2018 12:13:12 -0300 Subject: [pytest-dev] Disable pushing directly to features and master branches Message-ID: 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicholas+pytest at nicholaswilliams.net Fri Jul 6 11:15:16 2018 From: nicholas+pytest at nicholaswilliams.net (Nicholas Williams) Date: Fri, 6 Jul 2018 10:15:16 -0500 Subject: [pytest-dev] Disable pushing directly to features and master branches In-Reply-To: References: Message-ID: +1 On Fri, Jul 6, 2018 at 10:13 AM, Bruno Oliveira wrote: > 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. > > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Fri Jul 6 11:19:04 2018 From: me at the-compiler.org (Florian Bruhin) Date: Fri, 6 Jul 2018 17:19:04 +0200 Subject: [pytest-dev] Disable pushing directly to features and master branches In-Reply-To: References: Message-ID: <20180706151904.goznuz3vdllzyavb@hooch.localdomain> On Fri, Jul 06, 2018 at 12:13:12PM -0300, Bruno Oliveira wrote: > 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. Sounds like a great idea! Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From opensource at ronnypfannschmidt.de Fri Jul 6 11:26:26 2018 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Fri, 06 Jul 2018 17:26:26 +0200 Subject: [pytest-dev] Disable pushing directly to features and master branches In-Reply-To: References: Message-ID: +1 Am 6. Juli 2018 17:15:16 MESZ schrieb Nicholas Williams : >+1 > >On Fri, Jul 6, 2018 at 10:13 AM, Bruno Oliveira >wrote: > >> 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. >> >> >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Fri Jul 6 11:26:26 2018 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Fri, 06 Jul 2018 17:26:26 +0200 Subject: [pytest-dev] Disable pushing directly to features and master branches In-Reply-To: References: Message-ID: +1 Am 6. Juli 2018 17:15:16 MESZ schrieb Nicholas Williams : >+1 > >On Fri, Jul 6, 2018 at 10:13 AM, Bruno Oliveira >wrote: > >> 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. >> >> >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jul 6 11:29:01 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 6 Jul 2018 12:29:01 -0300 Subject: [pytest-dev] [PROPOSAL] switchgin over from gitmate via pytestbot to gitmate as an github app In-Reply-To: References: Message-ID: Hi Ronny, (Missed this email somehow) Are there any visible differences, aside from the comments being made by some GitMade bot account instead of pytestbot? Cheers On Sun, Jul 1, 2018 at 9:24 AM RonnyPfannschmidt < opensource at ronnypfannschmidt.de> wrote: > 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 > > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Fri Jul 6 14:38:15 2018 From: flub at devork.be (Floris Bruynooghe) Date: Fri, 06 Jul 2018 20:38:15 +0200 Subject: [pytest-dev] Disable pushing directly to features and master branches In-Reply-To: References: Message-ID: <87lgaonrag.fsf@powell.devork.be> On Fri 06 Jul 2018 at 12:13 -0300, Bruno Oliveira wrote: > 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). Oh, this is sad. It's the only way I manage to vaguely keep track of activity in pytest. I'll even less know what's going on now. > 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? Sure, +1 on this part From opensource at ronnypfannschmidt.de Fri Jul 6 16:05:46 2018 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Fri, 6 Jul 2018 22:05:46 +0200 Subject: [pytest-dev] [PROPOSAL] switchgin over from gitmate via pytestbot to gitmate as an github app In-Reply-To: References: Message-ID: <2ff0f281-6a77-8dcb-c690-60a4cc44da5f@ronnypfannschmidt.de> not that i'm aware of, but given the regular mislabeling i'm considering disabling it altogether instead -- Ronny Am 06.07.2018 um 17:29 schrieb Bruno Oliveira: > Hi Ronny, > > (Missed this email somehow) > > Are there any visible differences, aside from the comments being made by > some GitMade bot account instead of pytestbot? > > Cheers > > On Sun, Jul 1, 2018 at 9:24 AM RonnyPfannschmidt > > wrote: > > 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 > > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From me at the-compiler.org Fri Jul 6 16:30:18 2018 From: me at the-compiler.org (Florian Bruhin) Date: Fri, 6 Jul 2018 22:30:18 +0200 Subject: [pytest-dev] [PROPOSAL] switchgin over from gitmate via pytestbot to gitmate as an github app In-Reply-To: <2ff0f281-6a77-8dcb-c690-60a4cc44da5f@ronnypfannschmidt.de> References: <2ff0f281-6a77-8dcb-c690-60a4cc44da5f@ronnypfannschmidt.de> Message-ID: <20180706203018.5syfmplqf4dcwpwv@hooch.localdomain> On Fri, Jul 06, 2018 at 10:05:46PM +0200, RonnyPfannschmidt wrote: > not that i'm aware of, > but given the regular mislabeling i'm considering disabling it > altogether instead I did disable linking of related issues and automatic applying of labels a while ago for qutebrowser, because indeed it's just too wrong to be useful. It remains useful (for example for labelling PRs with "needs review"), but not sure if any useful functionality would remain for pytest. Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From oliver at bestwalter.de Fri Jul 6 20:54:31 2018 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Sat, 7 Jul 2018 02:54:31 +0200 Subject: [pytest-dev] Disable pushing directly to features and master branches In-Reply-To: <87lgaonrag.fsf@powell.devork.be> References: <87lgaonrag.fsf@powell.devork.be> Message-ID: sounds good. On Fri 6. Jul 2018 at 20:43, Floris Bruynooghe wrote: > On Fri 06 Jul 2018 at 12:13 -0300, Bruno Oliveira wrote: > > 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). > > Oh, this is sad. It's the only way I manage to vaguely keep track of > activity in pytest. I'll even less know what's going on now. > > > 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? > > Sure, +1 on this part > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jul 6 21:19:23 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 6 Jul 2018 22:19:23 -0300 Subject: [pytest-dev] Disable pushing directly to features and master branches In-Reply-To: References: <87lgaonrag.fsf@powell.devork.be> Message-ID: Thanks everyone for their input, it is enabled now! On Fri, Jul 6, 2018 at 9:54 PM Oliver Bestwalter wrote: > sounds good. > On Fri 6. Jul 2018 at 20:43, Floris Bruynooghe wrote: > >> On Fri 06 Jul 2018 at 12:13 -0300, Bruno Oliveira wrote: >> > 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). >> >> Oh, this is sad. It's the only way I manage to vaguely keep track of >> activity in pytest. I'll even less know what's going on now. >> >> > 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? >> >> Sure, +1 on this part >> > _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvain.marie at schneider-electric.com Fri Jul 27 12:31:59 2018 From: sylvain.marie at schneider-electric.com (Sylvain MARIE) Date: Fri, 27 Jul 2018 16:31:59 +0000 Subject: [pytest-dev] New plugin: pytest-steps Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From philosophe at gmail.com Sat Jul 28 18:12:30 2018 From: philosophe at gmail.com (Derek Sisson) Date: Sat, 28 Jul 2018 15:12:30 -0700 Subject: [pytest-dev] command line options not working? Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From they4kman at gmail.com Sun Jul 29 00:12:32 2018 From: they4kman at gmail.com (Zach Kanzler) Date: Sun, 29 Jul 2018 00:12:32 -0400 Subject: [pytest-dev] New plugin: pytest-lambda, or: lambda fixtures Message-ID: 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 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 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Sun Jul 29 03:07:43 2018 From: me at the-compiler.org (Florian Bruhin) Date: Sun, 29 Jul 2018 09:07:43 +0200 Subject: [pytest-dev] command line options not working? In-Reply-To: References: Message-ID: <20180729070743.bieilejab3ehbdip@hooch.localdomain> On Sat, Jul 28, 2018 at 03:12:30PM -0700, Derek Sisson wrote: > I've been using command line options for years, but they no longer work for > me. I get the message "unrecognized arguments". Works fine here (with 3.6.4 as well). > As a sanity check, I used the example from the documentation on > https://docs.pytest.org/en/latest/example/simple.html?highlight=addoption And you put that in a (correctly spelled) /Users/derek/dev/example/example/conftest.py file? Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From philosophe at gmail.com Sun Jul 29 10:35:43 2018 From: philosophe at gmail.com (Derek Sisson) Date: Sun, 29 Jul 2018 07:35:43 -0700 Subject: [pytest-dev] command line options not working? In-Reply-To: <20180729070743.bieilejab3ehbdip@hooch.localdomain> References: <20180729070743.bieilejab3ehbdip@hooch.localdomain> Message-ID: sigh. No, I put the command options into a configs.py file, because of problems I encountered 5 years ago getting options to work with other parameters, as documented here: https://stackoverflow.com/questions/15794038/unable-to-run-py-test-from-command-line-when-using-a-marker-and-text-fixture-opt Two years ago I refactored to stop using the separate runner.py file, and the comma options worked fine. Yes, moving the options into the conftest.py file works. I don't understand why the configs.py approach no longer works, but working code is a good resolution ;) thanks! --derek On Sun, Jul 29, 2018 at 12:07 AM, Florian Bruhin wrote: > On Sat, Jul 28, 2018 at 03:12:30PM -0700, Derek Sisson wrote: > > I've been using command line options for years, but they no longer work > for > > me. I get the message "unrecognized arguments". > > Works fine here (with 3.6.4 as well). > > > As a sanity check, I used the example from the documentation on > > https://docs.pytest.org/en/latest/example/simple.html? > highlight=addoption > > And you put that in a (correctly spelled) > /Users/derek/dev/example/example/conftest.py file? > > Florian > > -- > https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) > GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > I love long mails! | https://email.is-not-s.ms/ > -- thanks, --derek -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Mon Jul 30 19:42:36 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 30 Jul 2018 20:42:36 -0300 Subject: [pytest-dev] pytest 3.7.0 released! Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From florian.schulze at gmx.net Tue Jul 31 01:31:52 2018 From: florian.schulze at gmx.net (Florian Schulze) Date: Tue, 31 Jul 2018 07:31:52 +0200 Subject: [pytest-dev] pytest 3.7.0 released! In-Reply-To: References: Message-ID: <646E194D-A96C-4171-9566-AE27A65AC4A8@gmx.net> On 31 Jul 2018, at 1:42, Bruno Oliveira wrote: > The pytest team is proud to announce the 3.7.0 release! The new deprecation for directly called fixture functions promptly revealed cases where I accidentally did that. Thanks! Regards, Florian Schulze From alex at seedanddew.com Tue Jul 31 02:14:17 2018 From: alex at seedanddew.com (Alex Georgie) Date: Mon, 30 Jul 2018 23:14:17 -0700 Subject: [pytest-dev] Partnership possibility with Pytest Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Tue Jul 31 03:46:10 2018 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Tue, 31 Jul 2018 09:46:10 +0200 Subject: [pytest-dev] Partnership possibility with Pytest In-Reply-To: References: Message-ID: <56db90b0-9be4-ab6c-7bbf-38baef3c6cae@ronnypfannschmidt.de> Hi Alex, i like the Idea i`m def +1 on adding this and seeing how it plays out, Just to play devils advocate, are there any plans to adjust the cut should the financial situation ever allow it at scale? I`m also wondering if connecting parties in need of direct/indirect work on/with the project with freelancers/companies surrounding the projects is on the horizon. -- Ronny Am 31.07.2018 um 08:14 schrieb Alex Georgie: > 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 > > > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Tue Jul 31 04:23:58 2018 From: me at the-compiler.org (Florian Bruhin) Date: Tue, 31 Jul 2018 10:23:58 +0200 Subject: [pytest-dev] Partnership possibility with Pytest In-Reply-To: <56db90b0-9be4-ab6c-7bbf-38baef3c6cae@ronnypfannschmidt.de> References: <56db90b0-9be4-ab6c-7bbf-38baef3c6cae@ronnypfannschmidt.de> Message-ID: <20180731082358.62eomvrolypfadlx@hooch.localdomain> Hi, some random thoughts: FWIW I'm -1 on this (mainly because we don't have a good way to recieve and distribute money; and I doubt there is one at all), but currently a bit in a hurry. On Tue, Jul 31, 2018 at 09:46:10AM +0200, RonnyPfannschmidt wrote: > i like the Idea i`m def +1 on adding this and seeing how it plays out, Where would the money go? > 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. I'm also not sure if this works out. I use pytest a lot, but I rarely look at its documentation. At the same time, I might spend a lot of time looking at documentation of something I just want to try out but never use again. Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From dhunt at mozilla.com Tue Jul 31 07:53:51 2018 From: dhunt at mozilla.com (Dave Hunt) Date: Tue, 31 Jul 2018 12:53:51 +0100 Subject: [pytest-dev] Code of conduct for pytest organisation on GitHub Message-ID: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> 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 . Is there one documented elsewhere? If not, which should we adopt? Cheers, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From nicoddemus at gmail.com Tue Jul 31 08:00:25 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Tue, 31 Jul 2018 09:00:25 -0300 Subject: [pytest-dev] Code of conduct for pytest organisation on GitHub In-Reply-To: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> References: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> Message-ID: Hi Dave, On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt wrote: > 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. Is there one documented > elsewhere? If not, which should we adopt? > I'm a little surprised myself that we don't have one yet. I agree we should adopt one. Do you have a suggestion? Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhunt at mozilla.com Tue Jul 31 08:12:15 2018 From: dhunt at mozilla.com (Dave Hunt) Date: Tue, 31 Jul 2018 13:12:15 +0100 Subject: [pytest-dev] Code of conduct for pytest organisation on GitHub In-Reply-To: References: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> Message-ID: <78094116-1129-4690-BA84-2C9A3CAA2B58@mozilla.com> https://www.contributor-covenant.org/version/1/4/code-of-conduct.html looks like a good place to start. > On 31 Jul 2018, at 13:00, Bruno Oliveira wrote: > > Hi Dave, > > > On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt > wrote: > 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 . Is there one documented elsewhere? If not, which should we adopt? > > I'm a little surprised myself that we don't have one yet. I agree we should adopt one. Do you have a suggestion? > > Cheers, > Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From opensource at ronnypfannschmidt.de Tue Jul 31 08:18:06 2018 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Tue, 31 Jul 2018 14:18:06 +0200 Subject: [pytest-dev] Code of conduct for pytest organisation on GitHub In-Reply-To: <78094116-1129-4690-BA84-2C9A3CAA2B58@mozilla.com> References: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> <78094116-1129-4690-BA84-2C9A3CAA2B58@mozilla.com> Message-ID: <7fb2cb70-5321-004b-02fc-4d58bb29a8ae@ronnypfannschmidt.de> Hi all, i'd like to note that the C4 process has a general bad actor handling mechanism as well. i vaguely recall there have been various instances to bully projects into stuff like the contributors covenant, so personally i`m against conduct template that are associated with zealots pushing for them aggressively. i will try to substantiate this claim/memory with actual data later today. in case i can*t follow up today please consider it without merit until a demonstration is provided. -- Ronny Am 31.07.2018 um 14:12 schrieb Dave Hunt: > https://www.contributor-covenant.org/version/1/4/code-of-conduct.html?looks > like a good place to start. > >> On 31 Jul 2018, at 13:00, Bruno Oliveira > > wrote: >> >> Hi Dave, >> >> >> On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt > > wrote: >> >> 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. Is there one >> documented elsewhere? If not, which should we adopt? >> >> >> I'm a little surprised myself that we don't have one yet. I agree we >> should adopt one. Do you have a suggestion? >> >> Cheers, >> Bruno. > > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex at seedanddew.com Tue Jul 31 12:13:01 2018 From: alex at seedanddew.com (Alex Georgie) Date: Tue, 31 Jul 2018 09:13:01 -0700 Subject: [pytest-dev] Partnership possibility with Pytest In-Reply-To: <20180731082358.62eomvrolypfadlx@hooch.localdomain> References: <56db90b0-9be4-ab6c-7bbf-38baef3c6cae@ronnypfannschmidt.de> <20180731082358.62eomvrolypfadlx@hooch.localdomain> Message-ID: Hey guys, >are there any plans to adjust the cut should the financial situation ever allow it at scale? I haven't given this much thought but it's an option >I`m also wondering if connecting parties in need of direct/indirect work on/with the project with freelancers/companies surrounding the projects is on the horizon. Can you explain this again? I'm not sure I understand it. >Where would the money go? We actually work with an organization called OpenCollective ( https://opencollective.com/) that creates a non-profit for you. The idea is they handle the legalese and create an account where donations can go. All donations and expenses are also on the site, so it becomes fully transparent. I believe their cost structure is 5% of donations. We can send money straight to them. Does that work for you guys? >I'm also not sure if this works out. I use pytest a lot, but I rarely >look at its documentation. Not even as reference? Does that apply to other projects where you're not a dev as well? I've heard this feedback before and its fair but my hypothesis is that people still go back every now and then for reference and this applies evenly across all projects, so it should lead to the same proportion of revenue on a larger time frame. >At the same time, I might spend a lot of time >looking at documentation of something I just want to try out but never >use again. This seems fair too. You will be giving this project a one time burst of revenue and then never come back. In the longer time frame this should mean less revenue for the unused project and more for the one you actually use. I would actually consider this a feature since that small project gets something. In the current world, larger, more established projects and those that are good at marketing their funding requirements tend to get a lions share of donations while smaller projects get next to nothing. Our approach is to try to increase the pool of people that make those donations and allows the smaller projects to get some piece of that as well. Does that seem fair? Alex On Tue, Jul 31, 2018 at 1:23 AM, Florian Bruhin wrote: > Hi, > > some random thoughts: > > FWIW I'm -1 on this (mainly because we don't have a good way to recieve > and distribute money; and I doubt there is one at all), but currently a > bit in a hurry. > > On Tue, Jul 31, 2018 at 09:46:10AM +0200, RonnyPfannschmidt wrote: > > i like the Idea i`m def +1 on adding this and seeing how it plays out, > > Where would the money go? > > > 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. > > I'm also not sure if this works out. I use pytest a lot, but I rarely > look at its documentation. At the same time, I might spend a lot of time > looking at documentation of something I just want to try out but never > use again. > > Florian > > -- > https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) > GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > I love long mails! | https://email.is-not-s.ms/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Tue Jul 31 14:12:10 2018 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 31 Jul 2018 20:12:10 +0200 Subject: [pytest-dev] Code of conduct for pytest organisation on GitHub In-Reply-To: <7fb2cb70-5321-004b-02fc-4d58bb29a8ae@ronnypfannschmidt.de> References: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> <78094116-1129-4690-BA84-2C9A3CAA2B58@mozilla.com> <7fb2cb70-5321-004b-02fc-4d58bb29a8ae@ronnypfannschmidt.de> Message-ID: <87lg9ruvet.fsf@powell.devork.be> Hi, I'm agree that we should probably have a code of conduct. We had one for the sprint (we used https://www.python.org/psf/codeofconduct/ + 2 contact details for violations) and I'm surprised it stopped at the sprint. Probably an oversight. I just skimmed through C4 again and didn't spot much useful there, in any case the bulk of C4 does not try to address people's conduct. And the language used there is not very suitable for a code of conduct I think. So I'd rather adopt another one. So as to which one to adopt I'm not sure. The PSF one doesn't say anything about enforcement, which may not be ideal. The PyconUK one isn't bad either I think. But if Dave thinks the contributor-covenant is a good choice I'm happy to support that. Cheers, Floris On Tue 31 Jul 2018 at 14:18 +0200, RonnyPfannschmidt wrote: > Hi all, > > > i'd like to note that the C4 process has a general bad actor handling > mechanism as well. > > i vaguely recall there have been various instances to bully projects > into stuff like the contributors covenant, > so personally i`m against conduct template that are associated with > zealots pushing for them aggressively. > > i will try to substantiate this claim/memory with actual data later > today. in case i can*t follow up today please consider it without merit > until a demonstration is provided. > > -- Ronny > > > Am 31.07.2018 um 14:12 schrieb Dave Hunt: >> https://www.contributor-covenant.org/version/1/4/code-of-conduct.html?looks >> like a good place to start. >> >>> On 31 Jul 2018, at 13:00, Bruno Oliveira >> > wrote: >>> >>> Hi Dave, >>> >>> >>> On Tue, Jul 31, 2018 at 8:54 AM Dave Hunt >> > wrote: >>> >>> 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. Is there one >>> documented elsewhere? If not, which should we adopt? >>> >>> >>> I'm a little surprised myself that we don't have one yet. I agree we >>> should adopt one. Do you have a suggestion? >>> >>> Cheers, >>> Bruno. >> >> >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From flub at devork.be Tue Jul 31 14:28:05 2018 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 31 Jul 2018 20:28:05 +0200 Subject: [pytest-dev] Partnership possibility with Pytest In-Reply-To: References: Message-ID: <87in4vuuoa.fsf@powell.devork.be> Hi, On Mon 30 Jul 2018 at 23:14 -0700, Alex Georgie wrote: [...] > *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. So every single visitor of pytest.org will be continuously pinging your service? Regardless of being able to make this GDPR compliant that is still not something I feel comfortable with to decide for our users. Which made me check current pytest.org and it includes readthedocs analytics (probably fair enough) as well as a Google analytics bit. Anyone in control of this google one? Do we have use for it? Could we remove it? (I also had a bunch of other considerations mostly voiced already) Cheers, Floris From me at the-compiler.org Tue Jul 31 14:51:43 2018 From: me at the-compiler.org (Florian Bruhin) Date: Tue, 31 Jul 2018 20:51:43 +0200 Subject: [pytest-dev] Code of conduct for pytest organisation on GitHub In-Reply-To: <87lg9ruvet.fsf@powell.devork.be> References: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> <78094116-1129-4690-BA84-2C9A3CAA2B58@mozilla.com> <7fb2cb70-5321-004b-02fc-4d58bb29a8ae@ronnypfannschmidt.de> <87lg9ruvet.fsf@powell.devork.be> Message-ID: <20180731185143.cgikamnr422gg7eo@hooch.localdomain> On Tue, Jul 31, 2018 at 08:12:10PM +0200, Floris Bruynooghe wrote: > I'm agree that we should probably have a code of conduct. We had one > for the sprint (we used https://www.python.org/psf/codeofconduct/ + 2 > contact details for violations) and I'm surprised it stopped at the > sprint. Probably an oversight. > > I just skimmed through C4 again and didn't spot much useful there, in > any case the bulk of C4 does not try to address people's conduct. And > the language used there is not very suitable for a code of conduct I > think. So I'd rather adopt another one. I fully agree (with both paragraphs)! > So as to which one to adopt I'm not sure. The PSF one doesn't say > anything about enforcement, which may not be ideal. The PyconUK one > isn't bad either I think. But if Dave thinks the contributor-covenant > is a good choice I'm happy to support that. The PyConUK one is worded for conferences, which doesn't seem a suitable choice for projects. We could of course rephrase it, but it's like with licenses - there are projects where a lot of people put a lot of thought into a given wording, so writing a homebrewed one is usually a bad idea. +1 for the Contributor Covenant. It's well established and crafted with a lot of attention to detail, with quite a big community[1]. I was initially sceptical about CoCs in general as well, but after spending months researching the topic from both sides and talking to a lot of people, it got clear to me that CoCs are a very good thing - even/especially in communites which are already very much welcoming and healty. (If needed, I can go into details in September - sorry, exams are coming closer and closer) [1] https://github.com/ContributorCovenant/contributor_covenant Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From nicoddemus at gmail.com Tue Jul 31 15:09:40 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Tue, 31 Jul 2018 16:09:40 -0300 Subject: [pytest-dev] Code of conduct for pytest organisation on GitHub In-Reply-To: <20180731185143.cgikamnr422gg7eo@hooch.localdomain> References: <5D313523-E69E-44F2-B89E-3C8C42F9B67A@mozilla.com> <78094116-1129-4690-BA84-2C9A3CAA2B58@mozilla.com> <7fb2cb70-5321-004b-02fc-4d58bb29a8ae@ronnypfannschmidt.de> <87lg9ruvet.fsf@powell.devork.be> <20180731185143.cgikamnr422gg7eo@hooch.localdomain> Message-ID: Howdy, On Tue, Jul 31, 2018 at 3:51 PM Florian Bruhin wrote: > I was initially sceptical about CoCs in general as well, but after > spending months researching the topic from both sides and talking to a > lot of people, it got clear to me that CoCs are a very good thing - > even/especially in communites which are already very much welcoming and > healty. > I did take a look at the code of conduct, seems good to me. If you want to go with it, you have my +1. Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Tue Jul 31 15:20:17 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Tue, 31 Jul 2018 16:20:17 -0300 Subject: [pytest-dev] Partnership possibility with Pytest In-Reply-To: <87in4vuuoa.fsf@powell.devork.be> References: <87in4vuuoa.fsf@powell.devork.be> Message-ID: Hi all, On Tue, Jul 31, 2018 at 3:28 PM Floris Bruynooghe wrote: > Hi, > > On Mon 30 Jul 2018 at 23:14 -0700, Alex Georgie wrote: > [...] > > *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. > > So every single visitor of pytest.org will be continuously pinging your > service? Regardless of being able to make this GDPR compliant that is > still not something I feel comfortable with to decide for our users. > My main concerns are: 1. How do we use this funding? Sprint and conferences could be a good use for this money. 2. How this would affect visitors, well put by Floris above. 3. Who would be responsible for handling the money? I took a look at OpenCollective as Alex's suggestion and I like what I saw, it seems they take care of the bureocracy and core members and then approve Expenses and Reimbursements, in a very open and transparent manner. At first I was leaning towards -1 on this, but with OpenCollective in the game I'm leaning more towards +1. Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Tue Jul 31 15:37:20 2018 From: me at the-compiler.org (Florian Bruhin) Date: Tue, 31 Jul 2018 21:37:20 +0200 Subject: [pytest-dev] Partnership possibility with Pytest In-Reply-To: References: <56db90b0-9be4-ab6c-7bbf-38baef3c6cae@ronnypfannschmidt.de> <20180731082358.62eomvrolypfadlx@hooch.localdomain> Message-ID: <20180731193720.2z3bpwypkvbtissq@hooch.localdomain> On Tue, Jul 31, 2018 at 09:13:01AM -0700, Alex Georgie wrote: > >Where would the money go? > We actually work with an organization called OpenCollective ( > https://opencollective.com/) that creates a non-profit for you. The idea is > they handle the legalese and create an account where donations can go. All > donations and expenses are also on the site, so it becomes fully > transparent. I believe their cost structure is 5% of donations. We can send > money straight to them. Does that work for you guys? https://opencollective.com/opensource claims 5% platform fee + 5% host fee + ~3% payment fee. So we're down to getting about 57% of funds ;-) It still doesn't answer the question what we actually would use funds for (but that's not for you to answer of course :D). The only reason I can see right now is future development sprints, where this likely won't yield enough, while another crowdfunding likely would work out very well. > >I'm also not sure if this works out. I use pytest a lot, but I rarely > >look at its documentation. > Not even as reference? Does that apply to other projects where you're not a > dev as well? I've heard this feedback before and its fair but my hypothesis > is that people still go back every now and then for reference and this > applies evenly across all projects, so it should lead to the same > proportion of revenue on a larger time frame. I might go back there for a quick look (not really for pytest because I know the features I use); but still, I probably wouldn't spend much time there. I guess it could still work out, but I feel like assigning/dividing funds manually (think Patreon) both results in a more fair distribution, and gives me control where my money actually goes, based on what I find most important/useful/... for what I do. Just my $0.02 though ;-) Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: