From holger at merlinux.eu Wed Jun 1 01:17:16 2016 From: holger at merlinux.eu (holger krekel) Date: Wed, 1 Jun 2016 07:17:16 +0200 Subject: [pytest-dev] Preserving capture fd from fixture setup? In-Reply-To: <87h9de87vi.fsf@thinkpad.rath.org> References: <874m9tj0z0.fsf@thinkpad.rath.org> <20160528055328.GB3580@uwanda> <87h9de87vi.fsf@thinkpad.rath.org> Message-ID: <20160601051716.GI5620@uwanda> On Tue, May 31, 2016 at 10:17 -0700, Nikolaus Rath wrote: > On May 28 2016, holger krekel wrote: > > Hi Nikolaus, > > > > On Thu, May 19, 2016 at 12:34 -0700, Nikolaus Rath wrote: > >> Hello, > >> > >> I am testing a server. I am starting the server in a subprocess from a > >> fixture, and then issue requests to it from various tests. Unfortunately > >> this seems to have one big drawback: when a test fails, the capture > >> plugin does not display any output from the server process. > >> > >> After looking at the code, I think this is because the capture plugin > >> creates a new file descriptor for each test phase (setup, call, > >> teardown). > > > > it reuses the same file descriptor for capturing IIRC. After each > > phase (setup, call, teardown) the FD is reset to position 0. > > Hmm. Yeah, on closer inspection my test case was flawed - adding a > .flush() at the end of the setup code made the output appear in the > right spot. But my original problem remains. > > > > Is your problem that the server is started during fixture setup > > and you'd like to see its standard out/err during the test call phase? > > Exactly. I guess you could write some conftest.py hook which transfers the output from the setup phase to the call phase so you can see it when a test call phase fails. Something like: https://pytest.org/latest/example/simple.html#making-test-result-information-available-in-fixtures shows a bit of the mechanics for that although it is not precisely yet what you are asking for. It's probably a good idea to make it easier to show setup/fixture output during a test call failure. Showing all fixture output by default would be a bit much, though. Also, if a fixture is setup with a non-function caching scope one needs to memorize output differently because a test call phase then relates to a setup phase of a different test ... this is probably all worth a discussion at the upcoming sprint ... best, holger > > Best, > -Nikolaus > > -- > GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F > Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > ?Time flies like an arrow, fruit flies like a Banana.? > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From opensource at ronnypfannschmidt.de Wed Jun 1 01:59:54 2016 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Wed, 1 Jun 2016 07:59:54 +0200 Subject: [pytest-dev] py.test 2.9.2 released Message-ID: pytest-2.9.2 ============ 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: Adam Chainz Benjamin Dopplinger Bruno Oliveira Florian Bruhin John Towler Martin Prusse Meng Jue MengJueM Omar Kohl Quentin Pradet Ronny Pfannschmidt Thomas G?ttler TomV Tyler Goodlet Happy testing, The py.test Development Team 2.9.2 (compared to 2.9.1) --------------------------- **Bug Fixes** * fix `#510`_: skip tests where one parameterize dimension was empty thanks Alex Stapleton for the Report and `@RonnyPfannschmidt`_ for the PR * Fix Xfail does not work with condition keyword argument. Thanks `@astraw38`_ for reporting the issue (`#1496`_) and `@tomviner`_ for PR the (`#1524`_). * Fix win32 path issue when puttinging custom config file with absolute path in ``pytest.main("-c your_absolute_path")``. * Fix maximum recursion depth detection when raised error class is not aware of unicode/encoded bytes. Thanks `@prusse-martin`_ for the PR (`#1506`_). * Fix ``pytest.mark.skip`` mark when used in strict mode. Thanks `@pquentin`_ for the PR and `@RonnyPfannschmidt`_ for showing how to fix the bug. * Minor improvements and fixes to the documentation. Thanks `@omarkohl`_ for the PR. * Fix ``--fixtures`` to show all fixture definitions as opposed to just one per fixture name. Thanks to `@hackebrot`_ for the PR. .. _#510: https://github.com/pytest-dev/pytest/issues/510 .. _#1506: https://github.com/pytest-dev/pytest/pull/1506 .. _#1496: https://github.com/pytest-dev/pytest/issue/1496 .. _#1524: https://github.com/pytest-dev/pytest/issue/1524 .. _ at prusse-martin: https://github.com/prusse-martin .. _ at astraw38: https://github.com/astraw38 -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Wed Jun 1 04:31:25 2016 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 1 Jun 2016 10:31:25 +0200 Subject: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs? Message-ID: <20160601083124.GA13934@tonks> Hi again ;) For the pytest crowdfunding[1], we also agreed to send out stickers and t-shirts to the backers. Since I'll order shirts and stickers for my own crowdfunding[2] soon, I was asked if I could take care of doing the same for pytest :D However, I'm not too much of a design guy - so would anyone be willing to do a design for stickers and shirts? I can just take the pytest logo and print that, but at least for the shirt something more creative might be nice - for example, Brianna Laugher came up with the nice "asserts before reverts". Anyone? Florian [1] http://igg.me/at/pytest-sprint [2] http://igg.me/at/qutebrowser -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From me at the-compiler.org Wed Jun 1 04:26:44 2016 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 1 Jun 2016 10:26:44 +0200 Subject: [pytest-dev] pytest pre-sprint Message-ID: <20160601082644.GZ13934@tonks> Hi, I was asked by Omar Kohl if I could do some (online) mentoring to get started with pytest development, and out of that the idea of doing a small pre-sprint did grow ;) I plan to come to Freiburg 15th (Wed) or 16th (Thu) morning, and then have some workshop/mentoring on Thu/Fri about the basics of how to contribute to pytest. Is anyone else interested in joining? If so, Holger has offered to do it at his place. Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From sebastian at adblockplus.org Wed Jun 1 06:08:21 2016 From: sebastian at adblockplus.org (Sebastian Noack) Date: Wed, 1 Jun 2016 12:08:21 +0200 Subject: [pytest-dev] Joining the sprint In-Reply-To: <20160531135535.GC5620@uwanda> References: <20160531135535.GC5620@uwanda> Message-ID: Awesome, thanks! I added myself and Jon to the wiki page. As for things to work on, frankly I didn't think about that yet. But I'm happy to help out with whatever needs to be done. Or perhaps I come up with something more specific until the sprint. Sebastian On Tue, May 31, 2016 at 3:55 PM, holger krekel wrote: > On Tue, May 31, 2016 at 11:35 +0000, Bruno Oliveira wrote: > > Hi Sebastian, > > > > Great to hear you guys would like to join us. You are certainly welcome, > > you should only confirm with Holger if the venue supports two more > > people before > > committing; since the place for the sprint has been arranged, more people > > than initially planned has joined so we might be getting out of space. > > Other than that it would be great to have you guys with us. > > yes, it's fine as long as it's not too many people dropping by for just > two days. I am pretty sure we'll be able to have enough sprint space (68 > qm room and i'll be asking soon if there is an extra room some of the > days). > > Sebastian, Please add yourself to the wiki with the dates you are bound to > come. > > best, > holger > > > > > > > > Do you guys already have some topics in mind that would you like to work > on > > the sprint? You can get and idea of the topics we plan to work on the > > indiegogo page: > > https://www.indiegogo.com/projects/python-testing-sprint-mid-2016 > > > > Cheers, > > > > On Tue, May 31, 2016 at 5:28 AM Sebastian Noack < > sebastian at adblockplus.org> > > wrote: > > > > > Hi, > > > > > > I'm the module owner of our Python based modules (i.e. sitescripts and > > > buildtools) at Adblock Plus. We recently started to use pytest and tox, > > > while I have been using pytest and tox for personal projects, like the > > > infamous python-goto, for quite a while now. And of course in jinja2, > where > > > I'm a committer as well. > > > > > > I and my colleague Jon would like to join the sprint on June 24th + > 25th, > > > if we are welcome? Unfortunately, we can not make it from the > beginning. We > > > wouldn't need any support for travel and accommodation. > > > > > > Sebastian > > > _______________________________________________ > > > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sa at gocept.com Wed Jun 1 07:23:12 2016 From: sa at gocept.com (Steffen Allner) Date: Wed, 1 Jun 2016 13:23:12 +0200 Subject: [pytest-dev] pytest pre-sprint In-Reply-To: <20160601082644.GZ13934@tonks> References: <20160601082644.GZ13934@tonks> Message-ID: On 01.06.2016 10:26, Florian Bruhin wrote: > Hi, Hi, > > I was asked by Omar Kohl if I could do some (online) mentoring to get > started with pytest development, and out of that the idea of doing a > small pre-sprint did grow ;) Basics about contributing to pytest sounds appealing to me. But I cannot make it earlier to Freiburg. > > I plan to come to Freiburg 15th (Wed) or 16th (Thu) morning, and then > have some workshop/mentoring on Thu/Fri about the basics of how to > contribute to pytest. 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 participants. Btw, is there already a loose schedule for the week or will we decide everything on ground? When do we reasonably meet then? > > Is anyone else interested in joining? If so, Holger has offered to do > it at his place. > > Florian > --Steffen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From kvas.it at gmail.com Wed Jun 1 07:36:47 2016 From: kvas.it at gmail.com (Vasily Kuznetsov) Date: Wed, 01 Jun 2016 11:36:47 +0000 Subject: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs? In-Reply-To: <20160601083124.GA13934@tonks> References: <20160601083124.GA13934@tonks> Message-ID: Hi Florian, I'm not a professional designer but I have designed and printed a few t-shirts and stickers. Perhaps I can help. What is the timeline for this, can we discuss it in more during the sprint (I'm coming) or is it kind of urgent? Cheers, Vasily On Wed, Jun 1, 2016 at 10:31 AM Florian Bruhin wrote: > Hi again ;) > > For the pytest crowdfunding[1], we also agreed to send out stickers > and t-shirts to the backers. > > Since I'll order shirts and stickers for my own crowdfunding[2] soon, > I was asked if I could take care of doing the same for pytest :D > > However, I'm not too much of a design guy - so would anyone be willing > to do a design for stickers and shirts? > > I can just take the pytest logo and print that, but at least for the > shirt something more creative might be nice - for example, > Brianna Laugher came up with the nice "asserts before reverts". > > Anyone? > > Florian > > [1] http://igg.me/at/pytest-sprint > [2] http://igg.me/at/qutebrowser > > -- > http://www.the-compiler.org | me at 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/ > _______________________________________________ > 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 Wed Jun 1 07:44:11 2016 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 01 Jun 2016 11:44:11 +0000 Subject: [pytest-dev] pytest pre-sprint In-Reply-To: References: <20160601082644.GZ13934@tonks> Message-ID: 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 > participants. > Good idea. I suppose after a kick-off where we bring up and discuss various topics to work on and then split in groups, this might be one of the groups. I suppose it would be brief though. Btw, is there already a loose schedule for the week or will we decide > everything on ground? > I'm not sure, I think Holger might have an idea for that already. When do we reasonably meet then? Good question. 9am to 5pm, with a pub afterwards? :) Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas at thomas-lotze.de Wed Jun 1 07:46:11 2016 From: thomas at thomas-lotze.de (Thomas Lotze) Date: Wed, 1 Jun 2016 13:46:11 +0200 Subject: [pytest-dev] pytest pre-sprint In-Reply-To: References: <20160601082644.GZ13934@tonks> Message-ID: <20160601134611.1c781913@alpha> Steffen Allner wrote: > Basics about contributing to pytest sounds appealing to me. But I cannot > make it earlier to Freiburg. Same here. > 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 > participants. If these basics go beyond the contribution guide on the pytest web site, something written would also be a good thing, both in general and for myself in this particular case since I'll likely not join the sprint before the middle of the week. Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From me at the-compiler.org Wed Jun 1 07:48:16 2016 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 1 Jun 2016 13:48:16 +0200 Subject: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs? In-Reply-To: References: <20160601083124.GA13934@tonks> Message-ID: <20160601114816.GH13934@tonks> Hey Vasily, * Vasily Kuznetsov [2016-06-01 11:36:47 +0000]: > I'm not a professional designer but I have designed and printed a few > t-shirts and stickers. Perhaps I can help. What is the timeline for this, > can we discuss it in more during the sprint (I'm coming) or is it kind of > urgent? Thanks for the offer! Might indeed make sense to look at it during the sprint. The crowdfunding page says "estimated June 2016", but if it's July until stuff ships out, so be it. A crowdfunding without delays is not something you usually see anyways :D Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From sivan at vitakka.co Wed Jun 1 08:04:05 2016 From: sivan at vitakka.co (Sivan Greenberg) Date: Wed, 1 Jun 2016 15:04:05 +0300 Subject: [pytest-dev] pytest pre-sprint In-Reply-To: <20160601082644.GZ13934@tonks> References: <20160601082644.GZ13934@tonks> Message-ID: excellent idea! -Sivan On Wed, Jun 1, 2016 at 11:26 AM, Florian Bruhin wrote: > Hi, > > I was asked by Omar Kohl if I could do some (online) mentoring to get > started with pytest development, and out of that the idea of doing a > small pre-sprint did grow ;) > > I plan to come to Freiburg 15th (Wed) or 16th (Thu) morning, and then > have some workshop/mentoring on Thu/Fri about the basics of how to > contribute to pytest. > > Is anyone else interested in joining? If so, Holger has offered to do > it at his place. > > Florian > > -- > http://www.the-compiler.org | me at 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/ > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -- Sivan Greenberg Co founder & CTO Vitakka Consulting -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Wed Jun 1 08:16:12 2016 From: holger at merlinux.eu (holger krekel) Date: Wed, 1 Jun 2016 14:16:12 +0200 Subject: [pytest-dev] pytest pre-sprint In-Reply-To: References: <20160601082644.GZ13934@tonks> Message-ID: <20160601121612.GS5620@uwanda> On Wed, Jun 01, 2016 at 11:44 +0000, Bruno Oliveira wrote: > 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 > > participants. > > > > Good idea. I suppose after a kick-off where we bring up and discuss various > topics to work on and then split in groups, this might be one of the > groups. I suppose it would be brief though. > > Btw, is there already a loose schedule for the week or will we decide > > everything on ground? > > > > I'm not sure, I think Holger might have an idea for that already. > > When do we reasonably meet then? > > > Good question. 9am to 5pm, with a pub afterwards? :) Monday-saturday 9am till 6pm is the basic timing with a large lunch break each day. At least one afternoon i suggest going around hiking or other outdoor activities. I guess this will be on wednesday but i'd also make it dependent on weather. holger > Cheers, > Bruno. > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From farmi at web.de Wed Jun 1 08:16:25 2016 From: farmi at web.de (Stefan Farmbauer) Date: Wed, 01 Jun 2016 12:16:25 +0000 Subject: [pytest-dev] pytest pre-sprint In-Reply-To: References: <20160601082644.GZ13934@tonks> Message-ID: Hello For me it is quite the same. I'm really interested but can only arrive at the 19th. On the first day of the sprint is a nice idea. Stefan Sivan Greenberg schrieb am Mi., 1. Juni 2016 14:04: > excellent idea! > > -Sivan > > On Wed, Jun 1, 2016 at 11:26 AM, Florian Bruhin > wrote: > >> Hi, >> >> I was asked by Omar Kohl if I could do some (online) mentoring to get >> started with pytest development, and out of that the idea of doing a >> small pre-sprint did grow ;) >> >> I plan to come to Freiburg 15th (Wed) or 16th (Thu) morning, and then >> have some workshop/mentoring on Thu/Fri about the basics of how to >> contribute to pytest. >> >> Is anyone else interested in joining? If so, Holger has offered to do >> it at his place. >> >> Florian >> >> -- >> http://www.the-compiler.org | me at 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/ >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> >> > > > -- > Sivan Greenberg > Co founder & CTO > Vitakka Consulting > _______________________________________________ > 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 oliver at bestwalter.de Wed Jun 1 14:52:50 2016 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Wed, 01 Jun 2016 18:52:50 +0000 Subject: [pytest-dev] pytest pre-sprint In-Reply-To: <20160601121612.GS5620@uwanda> References: <20160601082644.GZ13934@tonks> <20160601121612.GS5620@uwanda> Message-ID: Hi, thanks Florian - that sounds great. I would also appreciate that on the first sprint day. I will be arriving on the 19th in the afternoon. I a started working my way into the code base of pytest but I am also very interested in working on tox. Cheers Oliver On Wed, 1 Jun 2016 at 14:18 holger krekel wrote: > On Wed, Jun 01, 2016 at 11:44 +0000, Bruno Oliveira wrote: > > 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 > > > participants. > > > > > > > Good idea. I suppose after a kick-off where we bring up and discuss > various > > topics to work on and then split in groups, this might be one of the > > groups. I suppose it would be brief though. > > > > Btw, is there already a loose schedule for the week or will we decide > > > everything on ground? > > > > > > > I'm not sure, I think Holger might have an idea for that already. > > > > When do we reasonably meet then? > > > > > > Good question. 9am to 5pm, with a pub afterwards? :) > > Monday-saturday 9am till 6pm is the basic timing with a large lunch > break each day. At least one afternoon i suggest going around hiking or > other outdoor activities. I guess this will be on wednesday but i'd also > make it dependent on weather. > > holger > > > > > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Thu Jun 2 07:18:39 2016 From: me at the-compiler.org (Florian Bruhin) Date: Thu, 2 Jun 2016 13:18:39 +0200 Subject: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs? In-Reply-To: References: <20160601083124.GA13934@tonks> <20160601114816.GH13934@tonks> Message-ID: <20160602111839.GE429@tonks> Hi, (Cc'ing the list again because I'd appreciate some more opinions other than mine!) * Vasily Kuznetsov [2016-06-01 15:55:32 +0000]: > Sounds good. I'll probably already start thinking about it. A few questions > before I start. > > So we need a t-shirt and a sticker, right? Right. > Have you already thought about how this will be printed and where? It's > just that different places need different formats and/or have different > colour requirements depending on the printing process, so better to know in > advance. So for my crowdfunding, those are the two places where I'll probably print things, unless I find a good reason why I should not: Sticker: http://www.flyeralarm.com/ch/shop/configurator/index/id/34/aufkleber-outdoor.html Shirt: https://www.textil-grosshandel.eu/textildruck/ Someone (Floris) also mentioned a swedish (?) shop for stickers as an alternative, but I can't find the mail anymore. Either way, if I'm the one taking care of ordering them, it's probably going to be flyeralarm ;) > Which size and shape of the sticker do we need? For my crowdfunding I'll go for the DIN A8 one (5.2 x 7.4 cm) as everything else is bigger or round/square and I didn't want that. For pytest I guess something square would work well too, they have 2/3/4/5/9.8cm for those. I think 4 or 5cm would be nice. > Do you already have anything in mind for the design? For the stickers, probably just the logo? I know Holger linked a SVG version, but no idea where those mails went... For the shirt, as said, I really like Briannas "asserts before reverts". Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From kvas.it at gmail.com Thu Jun 2 08:13:23 2016 From: kvas.it at gmail.com (Vasily Kuznetsov) Date: Thu, 02 Jun 2016 12:13:23 +0000 Subject: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs? In-Reply-To: <20160602111839.GE429@tonks> References: <20160601083124.GA13934@tonks> <20160601114816.GH13934@tonks> <20160602111839.GE429@tonks> Message-ID: Ok, seems to be pretty clear. The SVG of the logo would be pretty useful, but it's not urgent, I can start without. "asserts before reverts" is pretty cool, I like it too. Another idea that I thought about is a t-shirt themed using the output of pytest, like the dots for passing tests and the green line made of equals signs with "1337 passed in 0.42 seconds"-like message in the middle. Not sure yet, how exactly it'd look, probably something pretty minimalistic, but it could be neat. Vasily On Thu, Jun 2, 2016 at 1:18 PM Florian Bruhin wrote: > Hi, > > (Cc'ing the list again because I'd appreciate some more opinions other > than mine!) > > * Vasily Kuznetsov [2016-06-01 15:55:32 +0000]: > > Sounds good. I'll probably already start thinking about it. A few > questions > > before I start. > > > > So we need a t-shirt and a sticker, right? > > Right. > > > Have you already thought about how this will be printed and where? It's > > just that different places need different formats and/or have different > > colour requirements depending on the printing process, so better to know > in > > advance. > > So for my crowdfunding, those are the two places where I'll probably > print things, unless I find a good reason why I should not: > > Sticker: > http://www.flyeralarm.com/ch/shop/configurator/index/id/34/aufkleber-outdoor.html > Shirt: https://www.textil-grosshandel.eu/textildruck/ > > Someone (Floris) also mentioned a swedish (?) shop for stickers as an > alternative, but I can't find the mail anymore. Either way, if I'm the > one taking care of ordering them, it's probably going to be flyeralarm > ;) > > > Which size and shape of the sticker do we need? > > For my crowdfunding I'll go for the DIN A8 one (5.2 x 7.4 cm) as > everything else is bigger or round/square and I didn't want that. > > For pytest I guess something square would work well too, they have > 2/3/4/5/9.8cm for those. I think 4 or 5cm would be nice. > > > Do you already have anything in mind for the design? > > For the stickers, probably just the logo? > > I know Holger linked a SVG version, but no idea where those mails > went... > > For the shirt, as said, I really like Briannas > "asserts before reverts". > > Florian > > -- > http://www.the-compiler.org | me at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhunt at mozilla.com Thu Jun 2 09:20:53 2016 From: dhunt at mozilla.com (Dave Hunt) Date: Thu, 2 Jun 2016 14:20:53 +0100 Subject: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs? In-Reply-To: References: <20160601083124.GA13934@tonks> <20160601114816.GH13934@tonks> <20160602111839.GE429@tonks> Message-ID: <1233D781-483F-45A6-AB1B-848F8BBDCB18@mozilla.com> > On 2 Jun 2016, at 13:13, Vasily Kuznetsov wrote: > > "1337 passed in 0.42 seconds" <3 this -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Thu Jun 2 11:33:33 2016 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 02 Jun 2016 15:33:33 +0000 Subject: [pytest-dev] pytest crowdfunding: t-shirt/sticker designs? In-Reply-To: <1233D781-483F-45A6-AB1B-848F8BBDCB18@mozilla.com> References: <20160601083124.GA13934@tonks> <20160601114816.GH13934@tonks> <20160602111839.GE429@tonks> <1233D781-483F-45A6-AB1B-848F8BBDCB18@mozilla.com> Message-ID: 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, > _______________________________________________ > 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 Nikolaus at rath.org Sun Jun 5 14:37:38 2016 From: Nikolaus at rath.org (Nikolaus Rath) Date: Sun, 05 Jun 2016 14:37:38 -0400 Subject: [pytest-dev] Preserving capture fd from fixture setup? In-Reply-To: <20160601051716.GI5620@uwanda> (holger krekel's message of "Wed, 1 Jun 2016 07:17:16 +0200") References: <874m9tj0z0.fsf@thinkpad.rath.org> <20160528055328.GB3580@uwanda> <87h9de87vi.fsf@thinkpad.rath.org> <20160601051716.GI5620@uwanda> Message-ID: <87r3cbxz0t.fsf@kosh.rath.org> On Jun 01 2016, holger krekel wrote: > On Tue, May 31, 2016 at 10:17 -0700, Nikolaus Rath wrote: >> On May 28 2016, holger krekel wrote: >> > Hi Nikolaus, >> > >> > On Thu, May 19, 2016 at 12:34 -0700, Nikolaus Rath wrote: >> >> Hello, >> >> >> >> I am testing a server. I am starting the server in a subprocess from a >> >> fixture, and then issue requests to it from various tests. Unfortunately >> >> this seems to have one big drawback: when a test fails, the capture >> >> plugin does not display any output from the server process. >> >> >> >> After looking at the code, I think this is because the capture plugin >> >> creates a new file descriptor for each test phase (setup, call, >> >> teardown). >> > >> > it reuses the same file descriptor for capturing IIRC. After each >> > phase (setup, call, teardown) the FD is reset to position 0. >> >> Hmm. Yeah, on closer inspection my test case was flawed - adding a >> .flush() at the end of the setup code made the output appear in the >> right spot. But my original problem remains. >> >> >> > Is your problem that the server is started during fixture setup >> > and you'd like to see its standard out/err during the test call phase? >> >> Exactly. > > I guess you could write some conftest.py hook which transfers the output > from the setup phase to the call phase so you can see it when a test call > phase fails. Something like: > > https://pytest.org/latest/example/simple.html#making-test-result-information-available-in-fixtures > > shows a bit of the mechanics for that although it is not > precisely yet what you are asking for. FWIW, this is what I'm now using (and it seems to work reasonably well): https://bitbucket.org/nikratio/python-llfuse/src/552c0ccdaa5fbeeb6d5e1907554ba8b0a2ba6972/test/pytest_checklogs.py?at=default&fileviewer=file-view-default#pytest_checklogs.py-122 It was a little surprising that I had to get the reference to the capture object via the plugin-manager. The fixture was unusable at this point because it seems to be initialized later. Best, Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F ?Time flies like an arrow, fruit flies like a Banana.? From sivan at vitakka.co Mon Jun 6 10:54:07 2016 From: sivan at vitakka.co (Sivan Greenberg) Date: Mon, 6 Jun 2016 17:54:07 +0300 Subject: [pytest-dev] Joining the sprint In-Reply-To: References: <20160531135535.GC5620@uwanda> Message-ID: Hi All, To my regrets I have to inform that I will not be able to attend the sprint despite my strong inclination. Some personal matters have come up that will keep me booked for the dates and so I have to pass. Thanks for the willingness to have me, I hope to be able to make it for the next event of py.test / tox. -Sivan On Wed, Jun 1, 2016 at 1:08 PM, Sebastian Noack wrote: > Awesome, thanks! I added myself and Jon to the wiki page. > > As for things to work on, frankly I didn't think about that yet. But I'm > happy to help out with whatever needs to be done. Or perhaps I come up with > something more specific until the sprint. > > Sebastian > > On Tue, May 31, 2016 at 3:55 PM, holger krekel wrote: > >> On Tue, May 31, 2016 at 11:35 +0000, Bruno Oliveira wrote: >> > Hi Sebastian, >> > >> > Great to hear you guys would like to join us. You are certainly welcome, >> > you should only confirm with Holger if the venue supports two more >> > people before >> > committing; since the place for the sprint has been arranged, more >> people >> > than initially planned has joined so we might be getting out of space. >> > Other than that it would be great to have you guys with us. >> >> yes, it's fine as long as it's not too many people dropping by for just >> two days. I am pretty sure we'll be able to have enough sprint space (68 >> qm room and i'll be asking soon if there is an extra room some of the >> days). >> >> Sebastian, Please add yourself to the wiki with the dates you are bound >> to come. >> >> best, >> holger >> >> >> >> >> > >> > Do you guys already have some topics in mind that would you like to >> work on >> > the sprint? You can get and idea of the topics we plan to work on the >> > indiegogo page: >> > https://www.indiegogo.com/projects/python-testing-sprint-mid-2016 >> > >> > Cheers, >> > >> > On Tue, May 31, 2016 at 5:28 AM Sebastian Noack < >> sebastian at adblockplus.org> >> > wrote: >> > >> > > Hi, >> > > >> > > I'm the module owner of our Python based modules (i.e. sitescripts and >> > > buildtools) at Adblock Plus. We recently started to use pytest and >> tox, >> > > while I have been using pytest and tox for personal projects, like the >> > > infamous python-goto, for quite a while now. And of course in jinja2, >> where >> > > I'm a committer as well. >> > > >> > > I and my colleague Jon would like to join the sprint on June 24th + >> 25th, >> > > if we are welcome? Unfortunately, we can not make it from the >> beginning. We >> > > wouldn't need any support for travel and accommodation. >> > > >> > > Sebastian >> > > _______________________________________________ >> > > 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 >> >> > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -- Sivan Greenberg Co founder & CTO Vitakka Consulting -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Tue Jun 7 06:57:07 2016 From: holger at merlinux.eu (holger krekel) Date: Tue, 7 Jun 2016 12:57:07 +0200 Subject: [pytest-dev] sprint logistics / food Message-ID: <20160607105707.GI4410@uwanda> Hey pytest/tox sprinters, wrt to our current wiki planning here: https://github.com/pytest-dev/pytest/wiki/sprint2016 i'd like all attendees to check once again preferably until thursday: - i added a food column, could you all until thursday this week fill in the column e.g. with "ALL", "no-meat", "vegetarian", "vegan"? If your column is not changed till thursday i am going to assume "vegetarian". This is important because i am going to tell the Haus-am-Schoenberg, where the sprint is, for their lunch cooking (we get lunch every day, maybe not on wednesday). - Then, as to accomodation i'd like to get a clear picture what exactly is still needed. Please check your accomodation column. I assume that where people have "private" that it's settled. And where it's shared/wanted that it's still open -- that would be 7-8 people (depending on Andreas). At least Ana/Brianna and Florian can stay around my place as things stand. So we'd need a second flat for 4-5 persons IISIC. - three people (ronny, Danielle, NN/Splunk) have not updated their travel details yet -- could you do so? If anyone has any other questions, please post them here. cheers, holger From sa at gocept.com Tue Jun 7 10:00:26 2016 From: sa at gocept.com (Steffen Allner) Date: Tue, 7 Jun 2016 16:00:26 +0200 Subject: [pytest-dev] sprint logistics / food In-Reply-To: <20160607105707.GI4410@uwanda> References: <20160607105707.GI4410@uwanda> Message-ID: <6f688dde-4929-3b9a-54db-d91e9e9fd8b6@gocept.com> On 07.06.2016 12:57, holger krekel wrote: > Hey pytest/tox sprinters, Ahoi Holger, > > wrt to our current wiki planning here: > > https://github.com/pytest-dev/pytest/wiki/sprint2016 > > i'd like all attendees to check once again preferably until thursday: > > - i added a food column, could you all until thursday this week fill in > the column e.g. with "ALL", "no-meat", "vegetarian", "vegan"? > If your column is not changed till thursday i am going to assume "vegetarian". > This is important because i am going to tell the Haus-am-Schoenberg, where > the sprint is, for their lunch cooking (we get lunch every day, maybe not > on wednesday). > > - Then, as to accomodation i'd like to get a clear picture what exactly > is still needed. Please check your accomodation column. I assume > that where people have "private" that it's settled. And where it's > shared/wanted that it's still open -- that would be 7-8 people > (depending on Andreas). At least Ana/Brianna and Florian can stay > around my place as things stand. So we'd need a second flat for 4-5 > persons IISIC. > > - three people (ronny, Danielle, NN/Splunk) have not updated their > travel details yet -- could you do so? Thanks for organizing, I updated my data. > > If anyone has any other questions, please post them here. As I am still a bit unsure about the beginning and possible pre-events. So officially the sprint is on Monday 20th till Saturday 25th. Have you planned anything for the weekend before? Otherwise I might stay in Switzerland a day longer. > > cheers, > holger See you there, Steffen From brianna.laugher at gmail.com Wed Jun 8 10:07:34 2016 From: brianna.laugher at gmail.com (Brianna Laugher) Date: Thu, 9 Jun 2016 00:07:34 +1000 Subject: [pytest-dev] sprint logistics / food In-Reply-To: <20160607105707.GI4410@uwanda> References: <20160607105707.GI4410@uwanda> Message-ID: Yes I am leaving Australia Saturday and would like to know soon that I have a bed somewhere. :) I'm not travelling directly to the sprints so I have some flexibility on when I arrive, but basically plan to arrive on the 19th. thanks! exciting!! :D Brianna On 7 June 2016 at 20:57, holger krekel wrote: > Hey pytest/tox sprinters, > > wrt to our current wiki planning here: > > https://github.com/pytest-dev/pytest/wiki/sprint2016 > > i'd like all attendees to check once again preferably until thursday: > > - i added a food column, could you all until thursday this week fill in > the column e.g. with "ALL", "no-meat", "vegetarian", "vegan"? > If your column is not changed till thursday i am going to assume > "vegetarian". > This is important because i am going to tell the Haus-am-Schoenberg, > where > the sprint is, for their lunch cooking (we get lunch every day, maybe not > on wednesday). > > - Then, as to accomodation i'd like to get a clear picture what exactly > is still needed. Please check your accomodation column. I assume > that where people have "private" that it's settled. And where it's > shared/wanted that it's still open -- that would be 7-8 people > (depending on Andreas). At least Ana/Brianna and Florian can stay > around my place as things stand. So we'd need a second flat for 4-5 > persons IISIC. > > - three people (ronny, Danielle, NN/Splunk) have not updated their > travel details yet -- could you do so? > > If anyone has any other questions, please post them here. > > cheers, > holger > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -- They've just been waiting in a mountain for the right moment: http://modernthings.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at pelme.se Thu Jun 9 01:07:07 2016 From: andreas at pelme.se (Andreas Pelme) Date: Wed, 8 Jun 2016 22:07:07 -0700 Subject: [pytest-dev] sprint logistics / food In-Reply-To: <20160607105707.GI4410@uwanda> References: <20160607105707.GI4410@uwanda> Message-ID: Hello, > - Then, as to accomodation i'd like to get a clear picture what exactly > is still needed. Please check your accomodation column. I assume > that where people have "private" that it's settled. And where it's > shared/wanted that it's still open -- that would be 7-8 people > (depending on Andreas). At least Ana/Brianna and Florian can stay > around my place as things stand. So we'd need a second flat for 4-5 > persons IISIC. I?ve updated the wiki with my details. I booked a room 19th-26th that has two extra beds available. Looking forward seeing you all soon! :) Andreas From me at the-compiler.org Fri Jun 10 03:12:59 2016 From: me at the-compiler.org (Florian Bruhin) Date: Fri, 10 Jun 2016 09:12:59 +0200 Subject: [pytest-dev] My gripes with pytest and tox Message-ID: <20160610071259.2zo7dau23chlr7ol@tonks> Hi, What's following here are a few thoughts about things I miss or dislike about pytest, plugins I use, and tox. This is a list of things I personally would like to get fixed during the sprint, but of course that's not the only thing I want to work on, then I wouldn't need a sprint with other people. ;) Let me mention again this is my *personal* view of things. You might disagree with some of it. That's okay. Let's not turn this into a bike-shedding for now, though feel free to reply privately if needed. This also is not a rant. It's just a reminder for myself and a todo list. All of this software is awesome! Those are all minor annoyances. Some of those items have issues open, some of them I haven't told anyone about yet. A few of them might not be solvable at all. I thought for some while whether to make this public or not, but figured, hey, why not. In no particular order: pytest - doesn't have an easy way to do printf-style debugging (without -s) - prints the exception before all other report output instead of after - segfaults in my testsuite when using pdb (haven't investigated yet, pdb++ works) - blows up in weird ways with ImportErrors in plugins - too much boilerplate with parametrized fixtures - too much boilerplate with parametrized tests (what about keyword arguments?) - has a weirdly structured documentation - is inconsistent with types and attributes in all of its API - has an unintuitive warning system, for devs and users - doesn't work on Windows with colors (for me), prints black on black - hides python warnings pytest-qt - doesn't have tests yet for its modeltest branch, which is why it isn't merged yet - doesn't have a way to check arguments of signals - doesn't work with PySide2 (which is in development) pytest-bdd - doesn't have an easy way to setup/teardown things before/after all tests in a .feature file - doesn't have a way of parametrizing tests I can get in my head - doesn't support markers with arguments in .feature files - doesn't have gherkin reporting thinking about writing an alternative which integrates an existing python bdd framework (behave or lettuce) to profit from everything those offer pytest-catchlog - is still not in pytest-dev or core or renamed to -logging - still doesn't have pytest-logging functionality integrated - has no easy way to check a list of log messages - has no way to fail tests on unexpected error logging messages pytest-xdist - breaks my testsuite in ways I don't understand - doesn't seem to have an easy way for per-job fixtures pytest-xvfb - is broken with Qt4 plugin ideas - good profiling of tests: What's slow in my testsuite? What's slow in my application? - new BDD plugin maybe, see above tox - takes too long until my tests start - doesn't detect changes in requirements.txt files - doesn't support comments in deps= with newer pip's - is too verbose (too much noise with single-line output, needs -q) - is too quiet (with -v I want to see pip output) Again - no offense to anyone, and I don't intend to start a bike-shedding ;) Looking forward to the sprint! Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From opensource at ronnypfannschmidt.de Fri Jun 10 03:38:42 2016 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Fri, 10 Jun 2016 09:38:42 +0200 Subject: [pytest-dev] My gripes with pytest and tox In-Reply-To: <20160610071259.2zo7dau23chlr7ol@tonks> References: <20160610071259.2zo7dau23chlr7ol@tonks> Message-ID: <66210a73-9172-4bc3-6cd2-11a6c467cb16@ronnypfannschmidt.de> Hi Florian, below i threw in some thoughts and strong opinions, take with a grain of salt and feel free to tear them down :) best, Ronny Am 10.06.2016 um 09:12 schrieb Florian Bruhin: > Hi, > > What's following here are a few thoughts about things I miss or > dislike about pytest, plugins I use, and tox. This is a list of things > I personally would like to get fixed during the sprint, but of course > that's not the only thing I want to work on, then I wouldn't need a > sprint with other people. ;) > > Let me mention again this is my *personal* view of things. You might > disagree with some of it. That's okay. Let's not turn this into a > bike-shedding for now, though feel free to reply privately if needed. > > This also is not a rant. It's just a reminder for myself and a todo > list. All of this software is awesome! Those are all minor annoyances. > > Some of those items have issues open, some of them I haven't told > anyone about yet. A few of them might not be solvable at all. > > I thought for some while whether to make this public or not, but > figured, hey, why not. > > In no particular order: > > pytest > - doesn't have an easy way to do printf-style debugging > (without -s) thats per design - you are supposed to leave prints in and use the output capture to get context i would prefer to extend on that instead of adding a new more limited way just because its convenient in some cases > - prints the exception before all other report output instead of > after perhaps it makes sense to order things based on number of lines, have a way to take control of that different kinds of testsuites have different kinds of output and debug help for somethings the exceptions are a better help, for others output traces are > - segfaults in my testsuite when using pdb (haven't investigated > yet, pdb++ works) i suspect a potential readline issue (pdb++ uses pyrepl instead of readline) please report > - blows up in weird ways with ImportErrors in plugins thats indeed a pluggy gripe, IMHO we should put pluggy under pytest-dev and extend it (i#d also like to cythonize it and publish manylinux/windows wheels) > - too much boilerplate with parametrized fixtures > - too much boilerplate with parametrized tests (what about keyword > arguments?) examples for those 2 items please, i saw them as convenient and boilerplate-removing and i'd love to see your new uses and pain points > - has a weirdly structured documentation agreed :/ > - is inconsistent with types and attributes in all of its API thats a product of growing more and more features while staying backward compatible, i'd love to collect, revisit and clean that up as well > - has an unintuitive warning system, for devs and users i think i have been more than vocal about being really unhappy about the warning system > - doesn't work on Windows with colors (for me), prints black on > black afair that needs colorama what can we do to improve? > - hides python warnings i consider that a bad bug and gripe personally i'd like to integrate python warnings and pytest warnings under a consistent track-able and python warnings compatible api > > pytest-qt > - doesn't have tests yet for its modeltest branch, which is why it > isn't merged yet > - doesn't have a way to check arguments of signals > - doesn't work with PySide2 (which is in development) > > pytest-bdd > - doesn't have an easy way to setup/teardown things before/after > all tests in a .feature file > - doesn't have a way of parametrizing tests I can get in my head > - doesn't support markers with arguments in .feature files > - doesn't have gherkin reporting > > thinking about writing an alternative which integrates an existing > python bdd framework (behave or lettuce) to profit from everything > those offer > > pytest-catchlog > - is still not in pytest-dev or core or renamed to -logging > - still doesn't have pytest-logging functionality integrated > - has no easy way to check a list of log messages > - has no way to fail tests on unexpected error logging messages > > pytest-xdist > - breaks my testsuite in ways I don't understand > - doesn't seem to have an easy way for per-job fixtures xdist has no "jobs" - as of now its simply running multiple sessions and schedules items between them based on strategies, my basic opinion is that the codebase completely outgrew the initial design and needs major internal changes and those a re pretty expensive in terms of time and its also not clear what model to use i'd love to discuss at the sprint > > pytest-xvfb > - is broken with Qt4 > > plugin ideas > - good profiling of tests: > What's slow in my testsuite? > What's slow in my application? > - new BDD plugin maybe, see above > > tox > - takes too long until my tests start > - doesn't detect changes in requirements.txt files > - doesn't support comments in deps= with newer pip's > - is too verbose > (too much noise with single-line output, needs -q) > - is too quiet (with -v I want to see pip output) > > Again - no offense to anyone, and I don't intend to start a > bike-shedding ;) > > Looking forward to the sprint! > > Florian > > > > _______________________________________________ > 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 Jun 10 04:00:53 2016 From: me at the-compiler.org (Florian Bruhin) Date: Fri, 10 Jun 2016 10:00:53 +0200 Subject: [pytest-dev] My gripes with pytest and tox In-Reply-To: <66210a73-9172-4bc3-6cd2-11a6c467cb16@ronnypfannschmidt.de> References: <20160610071259.2zo7dau23chlr7ol@tonks> <66210a73-9172-4bc3-6cd2-11a6c467cb16@ronnypfannschmidt.de> Message-ID: <20160610080053.qnjmz6hlosjs77eh@tonks> * Ronny Pfannschmidt [2016-06-10 09:38:42 +0200]: > Hi Florian, > > below i threw in some thoughts and strong opinions, > take with a grain of salt and feel free to tear them down :) Thanks! > Am 10.06.2016 um 09:12 schrieb Florian Bruhin: > > pytest > > - doesn't have an easy way to do printf-style debugging > > (without -s) > thats per design - you are supposed to leave prints in and use the > output capture to get context > i would prefer to extend on that instead of adding a new more limited > way just because its convenient in some cases Let's continue discussing this in the issue[1] or at the sprint :) [1] https://github.com/pytest-dev/pytest/issues/1602 > > - prints the exception before all other report output instead of > > after > perhaps it makes sense to order things based on number of lines, have a > way to take control of that > different kinds of testsuites have different kinds of output and debug help > > for somethings the exceptions are a better help, for others output > traces are True - I guess a config option would make sense. I often have hundreds of lines of (valuable!) logging in the report output, so I need to scroll up a lot to find out *what* went wrong in the first place. > > - segfaults in my testsuite when using pdb (haven't investigated > > yet, pdb++ works) > i suspect a potential readline issue (pdb++ uses pyrepl instead of > readline) please report I'll do, after getting my qutebrowser release out today :D > > - blows up in weird ways with ImportErrors in plugins > thats indeed a pluggy gripe, IMHO we should put pluggy under pytest-dev > and extend it (i#d also like to cythonize it and publish > manylinux/windows wheels) +1 > > - too much boilerplate with parametrized fixtures > > - too much boilerplate with parametrized tests (what about keyword > > arguments?) > examples for those 2 items please, i saw them as convenient and > boilerplate-removing and i'd love to see your new uses and pain points For test parametrizing I imagine something like: @pytest.mark.parametrize(inp=['one', 'two'], expected=[(1, True), (2, False)]) def test_numbers(inp, expected): assert number(inp) == expected instead of @pytest.mark.parametrize('inp, expected', [ ('one', (1, True)), ('two', (2, False)), ]) def test_numbers(inp, expected): assert number(inp) == expected Though with the current syntax, the parameters for one invocation are grouped together nicely. I need to think about it some more. For the fixtures, I often need to do something like: @pytest.fixture(params=['one', 'two']) def fixt(request): # ... return request.param I just wonder if there's a slightly cleaner way of doing this kind of thing. Maybe there isn't. Haven't given it much thought yet. > > - doesn't work on Windows with colors (for me), prints black on > > black > afair that needs colorama what can we do to improve? Yeah, it's with colorama. I just get black output in a black shell when running pytest and can only see anything with --color=no. It's a bug somewhere, but I haven't had time to investigate yet. > > - hides python warnings > i consider that a bad bug and gripe > personally i'd like to integrate python warnings and pytest warnings > under a consistent track-able and python warnings compatible api Sounds like a plan! Definitely a sprint item I presume. > > pytest-xdist > > - breaks my testsuite in ways I don't understand > > - doesn't seem to have an easy way for per-job fixtures > xdist has no "jobs" - as of now its simply running multiple sessions and > schedules items between them based on strategies, > my basic opinion is that the codebase completely outgrew the initial > design and needs major internal changes > and those a re pretty expensive in terms of time and its also not clear > what model to use I mean jobs as in the -j flag ;) Basically I run my code under test as a subprocess, and then send commands to it via IPC and check the log output. This means if I parallelize my tests (which I'd really want to!) I have four test-processes talking to one process under test, which gets confused. So I need an easy way to start four test processes and four subprocesses. Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From florian.schulze at gmx.net Fri Jun 10 04:36:34 2016 From: florian.schulze at gmx.net (Florian Schulze) Date: Fri, 10 Jun 2016 10:36:34 +0200 Subject: [pytest-dev] My gripes with pytest and tox In-Reply-To: <20160610080053.qnjmz6hlosjs77eh@tonks> References: <20160610071259.2zo7dau23chlr7ol@tonks> <66210a73-9172-4bc3-6cd2-11a6c467cb16@ronnypfannschmidt.de> <20160610080053.qnjmz6hlosjs77eh@tonks> Message-ID: > For the fixtures, I often need to do something like: > > @pytest.fixture(params=['one', 'two']) > def fixt(request): > # ... > return request.param > > I just wonder if there's a slightly cleaner way of doing this kind of > thing. Maybe there isn't. Haven't given it much thought yet. I would like if @pytest.mark.parametrize works with fixtures. Regards, Florian Schulze From flub at devork.be Fri Jun 10 05:20:30 2016 From: flub at devork.be (Floris Bruynooghe) Date: Fri, 10 Jun 2016 10:20:30 +0100 Subject: [pytest-dev] My gripes with pytest and tox In-Reply-To: References: <20160610071259.2zo7dau23chlr7ol@tonks> <66210a73-9172-4bc3-6cd2-11a6c467cb16@ronnypfannschmidt.de> <20160610080053.qnjmz6hlosjs77eh@tonks> Message-ID: On 10 June 2016 at 09:36, Florian Schulze wrote: > >> For the fixtures, I often need to do something like: >> >> @pytest.fixture(params=['one', 'two']) >> def fixt(request): >> # ... >> return request.param >> >> I just wonder if there's a slightly cleaner way of doing this kind of >> thing. Maybe there isn't. Haven't given it much thought yet. > > I would like if @pytest.mark.parametrize works with fixtures. I've always been an advocate of using @pytest.mark.foo only ever on test functions/classes and not other things. And yes there are some early violations of this, but IIRC they are no longer needed with pluggy. From holger at merlinux.eu Fri Jun 10 05:48:14 2016 From: holger at merlinux.eu (holger krekel) Date: Fri, 10 Jun 2016 11:48:14 +0200 Subject: [pytest-dev] sprint latest updates / food / code with conduct Message-ID: <20160610094814.GC4410@uwanda> I reordered attendees list by arrival times. Also added a code-with-conduct part which references the PSF code of conduct thing, see our coordination page: https://github.com/pytest-dev/pytest/wiki/sprint2016 As to food, 6 people have left XXX for food: Sebastian, Jon, Oleg, Omar, Daniel, Raphael. unless it changes today i am going to assume "vegetarian" for XXX. lunch is 13 euro per person and it's covered by the sprint budget for everyone. But it means i'd like to have somewhat fitting numbers and not waste food. here is the complete breakdown IISIC: June 20-22th 22 persons, 12 all, 3 vegetarian, 2 no-pork, 1 vegan, 4 xxx June 23-25th 25 persons, 13 all, 3 vegetarian, 2 no-pork, 1 vegan, 6 xxx I guess one day we are not going to take lunch because it's kind of a break day - likely the 22nd or 23rd, depending on weather -- which is whether fluid here currently. Jon, Sebastian, Thomas: do you have an idea at which time you arrive on the 23rd? If it's afternoon we could just make a meeting point in the late afternoon and otherwise consider it as candidate for break day for the others. besides, i am also currently arranging another flat for accomodation. I presume that those who said "share" are fine to share e.g. a room with two beddings. If not, get back to me privately. We'll find accomodatation for everybody, no worries :) best, holger (out now to enjoy sun as it's more rainy the next days ...) P.S.: could someone with worse weather lookup contact data at indiegogo or so for the "sprint influencers" (who gave 1500) and send it to me? I'd like to offer them a chat next week ... From thomas at thomas-lotze.de Fri Jun 10 06:24:46 2016 From: thomas at thomas-lotze.de (Thomas Lotze) Date: Fri, 10 Jun 2016 12:24:46 +0200 Subject: [pytest-dev] sprint latest updates / food / code with conduct In-Reply-To: <20160610094814.GC4410@uwanda> References: <20160610094814.GC4410@uwanda> Message-ID: <20160610122446.6a41a4a7@alpha> holger krekel wrote: > Jon, Sebastian, Thomas: do you have an idea at which time you > arrive on the 23rd? If it's afternoon we could just make a meeting > point in the late afternoon and otherwise consider it as candidate > for break day for the others. I could be there in the morning or afternoon, whichever fits you better. I plan to be in the area early in the morning, and given that I'll be at the sprint only part of the time anyway, I'd like to make the most of it. Let's communicate on the 22nd, when you know the plans for that day and the next. Cheers, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From me at the-compiler.org Fri Jun 10 06:37:12 2016 From: me at the-compiler.org (Florian Bruhin) Date: Fri, 10 Jun 2016 12:37:12 +0200 Subject: [pytest-dev] sprint latest updates / food / code with conduct In-Reply-To: <20160610094814.GC4410@uwanda> References: <20160610094814.GC4410@uwanda> Message-ID: <20160610103712.ekbeolj4kdewhomn@tonks> * holger krekel [2016-06-10 11:48:14 +0200]: > P.S.: could someone with worse weather lookup contact data at indiegogo > or so for the "sprint influencers" (who gave 1500) and send it to me? > I'd like to offer them a chat next week ... I'll take care of it, answering off-list. Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From raphael at hackebrot.de Fri Jun 10 06:30:05 2016 From: raphael at hackebrot.de (Raphael Pierzina) Date: Fri, 10 Jun 2016 11:30:05 +0100 Subject: [pytest-dev] sprint latest updates / food / code with conduct In-Reply-To: <20160610094814.GC4410@uwanda> References: <20160610094814.GC4410@uwanda> Message-ID: <6F5CC161-069E-4D2B-B0DE-0BC480DE4F5D@hackebrot.de> Hi Holger, sorry about that - I?ve updated my diet info in the wiki to ?vegetarian?. Thanks for taking care of this. Raphael > On 10 Jun 2016, at 10:48, holger krekel wrote: > > > I reordered attendees list by arrival times. > Also added a code-with-conduct part which references > the PSF code of conduct thing, see our coordination page: > > https://github.com/pytest-dev/pytest/wiki/sprint2016 > > As to food, 6 people have left XXX for food: Sebastian, Jon, Oleg, Omar, > Daniel, Raphael. unless it changes today i am going to assume > "vegetarian" for XXX. lunch is 13 euro per person and it's covered by > the sprint budget for everyone. But it means i'd like to have somewhat > fitting numbers and not waste food. here is the complete breakdown IISIC: > > June 20-22th 22 persons, 12 all, 3 vegetarian, 2 no-pork, 1 vegan, 4 xxx > June 23-25th 25 persons, 13 all, 3 vegetarian, 2 no-pork, 1 vegan, 6 xxx > > I guess one day we are not going to take lunch because it's kind of a > break day - likely the 22nd or 23rd, depending on weather -- which is > whether fluid here currently. > > Jon, Sebastian, Thomas: do you have an idea at which time you > arrive on the 23rd? If it's afternoon we could just make a meeting > point in the late afternoon and otherwise consider it as candidate > for break day for the others. > > besides, i am also currently arranging another flat for accomodation. > I presume that those who said "share" are fine to share > e.g. a room with two beddings. If not, get back to me privately. > We'll find accomodatation for everybody, no worries :) > > best, > holger (out now to enjoy sun as it's more rainy the next days ...) > > P.S.: could someone with worse weather lookup contact data at indiegogo > or so for the "sprint influencers" (who gave 1500) and send it to me? > I'd like to offer them a chat next week ... > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From flub at devork.be Fri Jun 10 06:58:16 2016 From: flub at devork.be (Floris Bruynooghe) Date: Fri, 10 Jun 2016 11:58:16 +0100 Subject: [pytest-dev] sprint latest updates / food / code with conduct In-Reply-To: <20160610094814.GC4410@uwanda> References: <20160610094814.GC4410@uwanda> Message-ID: On 10 June 2016 at 10:48, holger krekel wrote: > > I reordered attendees list by arrival times. > Also added a code-with-conduct part which references > the PSF code of conduct thing, see our coordination page: > > https://github.com/pytest-dev/pytest/wiki/sprint2016 > > As to food, 6 people have left XXX for food: Sebastian, Jon, Oleg, Omar, > Daniel, Raphael. unless it changes today i am going to assume > "vegetarian" for XXX. I'm reasonably sure Daniel is vegan. I've pinged him on twitter to update the wiki. From nicoddemus at gmail.com Fri Jun 10 08:15:43 2016 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 10 Jun 2016 12:15:43 +0000 Subject: [pytest-dev] sprint logistics / food In-Reply-To: <20160607105707.GI4410@uwanda> References: <20160607105707.GI4410@uwanda> Message-ID: 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 (thought about this thinking about reviewing the documentation structure). Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Nikolaus at rath.org Fri Jun 10 12:26:34 2016 From: Nikolaus at rath.org (Nikolaus Rath) Date: Fri, 10 Jun 2016 09:26:34 -0700 Subject: [pytest-dev] My gripes with pytest and tox In-Reply-To: <20160610071259.2zo7dau23chlr7ol@tonks> (Florian Bruhin's message of "Fri, 10 Jun 2016 09:12:59 +0200") References: <20160610071259.2zo7dau23chlr7ol@tonks> Message-ID: <87bn39t3gl.fsf@thinkpad.rath.org> On Jun 10 2016, Florian Bruhin wrote: > In no particular order: > > pytest > - has a weirdly structured documentation Very much agree. > pytest-catchlog > - is still not in pytest-dev or core or renamed to -logging > - still doesn't have pytest-logging functionality integrated > - has no easy way to check a list of log messages > - has no way to fail tests on unexpected error logging messages Agreed. I'm extended it with code like https://bitbucket.org/nikratio/python-llfuse/src/tip/test/pytest_checklogs.py, but I think there's no way to ever make this pretty without some changes to pytest. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F ?Time flies like an arrow, fruit flies like a Banana.? From kvas.it at gmail.com Fri Jun 10 12:56:53 2016 From: kvas.it at gmail.com (Vasily Kuznetsov) Date: Fri, 10 Jun 2016 16:56:53 +0000 Subject: [pytest-dev] sprint latest updates / food / code with conduct In-Reply-To: <20160610094814.GC4410@uwanda> References: <20160610094814.GC4410@uwanda> Message-ID: Hi Holger, Jon and Sebastian are traveling in the US now, so I think they've missed the email. I updated the food preferences for them in the wiki and checked the arrival time on the 23rd. They'll arrive by car in the afternoon. Cheers, Vasily On Fri, Jun 10, 2016, 10:48 holger krekel wrote: > > I reordered attendees list by arrival times. > Also added a code-with-conduct part which references > the PSF code of conduct thing, see our coordination page: > > https://github.com/pytest-dev/pytest/wiki/sprint2016 > > As to food, 6 people have left XXX for food: Sebastian, Jon, Oleg, Omar, > Daniel, Raphael. unless it changes today i am going to assume > "vegetarian" for XXX. lunch is 13 euro per person and it's covered by > the sprint budget for everyone. But it means i'd like to have somewhat > fitting numbers and not waste food. here is the complete breakdown IISIC: > > June 20-22th 22 persons, 12 all, 3 vegetarian, 2 no-pork, 1 vegan, 4 xxx > June 23-25th 25 persons, 13 all, 3 vegetarian, 2 no-pork, 1 vegan, 6 xxx > > I guess one day we are not going to take lunch because it's kind of a > break day - likely the 22nd or 23rd, depending on weather -- which is > whether fluid here currently. > > Jon, Sebastian, Thomas: do you have an idea at which time you > arrive on the 23rd? If it's afternoon we could just make a meeting > point in the late afternoon and otherwise consider it as candidate > for break day for the others. > > besides, i am also currently arranging another flat for accomodation. > I presume that those who said "share" are fine to share > e.g. a room with two beddings. If not, get back to me privately. > We'll find accomodatation for everybody, no worries :) > > best, > holger (out now to enjoy sun as it's more rainy the next days ...) > > P.S.: could someone with worse weather lookup contact data at indiegogo > or so for the "sprint influencers" (who gave 1500) and send it to me? > I'd like to offer them a chat next week ... > _______________________________________________ > 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 zimmermann.code at gmail.com Fri Jun 10 14:36:19 2016 From: zimmermann.code at gmail.com (Stefan Zimmermann) Date: Fri, 10 Jun 2016 18:36:19 +0000 Subject: [pytest-dev] Participation Message-ID: Hi Holger and all other members, I just want to tell that I'd also like to join the sprint. I hope it's not too late. At least I don't need any funding. And will eat what's left ;) I'm working as Python/C++/Java developer at ADVA Optical Networking SE in Meiningen, mainly related to RobotFramework-based test automation during the last 5 years, now with different tasks... We use pytest for all of our Python projects at work, and I do lots of open source development. So I have just no reason for not joining :) I'm looking forward to see you all. Cheers, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Fri Jun 10 17:37:20 2016 From: me at the-compiler.org (Florian Bruhin) Date: Fri, 10 Jun 2016 23:37:20 +0200 Subject: [pytest-dev] My gripes with pytest and tox In-Reply-To: <87bn39t3gl.fsf@thinkpad.rath.org> References: <20160610071259.2zo7dau23chlr7ol@tonks> <87bn39t3gl.fsf@thinkpad.rath.org> Message-ID: <20160610213719.ev6lfd4223crhl66@tonks> * Nikolaus Rath [2016-06-10 09:26:34 -0700]: > On Jun 10 2016, Florian Bruhin wrote: > > pytest-catchlog > > [...] > > - has no way to fail tests on unexpected error logging messages > > Agreed. I'm extended it with code like > https://bitbucket.org/nikratio/python-llfuse/src/tip/test/pytest_checklogs.py, > but I think there's no way to ever make this pretty without some changes > to pytest. Not to pytest, but to pytest-catchlog I think? I haven't taken a closer look at your code yet, but I have something like this too: https://github.com/The-Compiler/qutebrowser/blob/master/tests/helpers/logfail.py https://github.com/The-Compiler/qutebrowser/blob/master/tests/helpers/test_logfail.py The main problem is that it doesn't work with the git master of pytest-catchlog and I couldn't get it to work when I tried last time. Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From Nikolaus at rath.org Fri Jun 10 18:29:35 2016 From: Nikolaus at rath.org (Nikolaus Rath) Date: Fri, 10 Jun 2016 15:29:35 -0700 Subject: [pytest-dev] My gripes with pytest and tox In-Reply-To: <20160610213719.ev6lfd4223crhl66@tonks> (Florian Bruhin's message of "Fri, 10 Jun 2016 23:37:20 +0200") References: <20160610071259.2zo7dau23chlr7ol@tonks> <87bn39t3gl.fsf@thinkpad.rath.org> <20160610213719.ev6lfd4223crhl66@tonks> Message-ID: <8760tgu180.fsf@thinkpad.rath.org> On Jun 10 2016, Florian Bruhin wrote: > * Nikolaus Rath [2016-06-10 09:26:34 -0700]: >> On Jun 10 2016, Florian Bruhin wrote: >> > pytest-catchlog >> > [...] >> > - has no way to fail tests on unexpected error logging messages >> >> Agreed. I'm extended it with code like >> https://bitbucket.org/nikratio/python-llfuse/src/tip/test/pytest_checklogs.py, >> but I think there's no way to ever make this pretty without some changes >> to pytest. > > Not to pytest, but to pytest-catchlog I think? > > I haven't taken a closer look at your code yet, but I have something > like this too: > > https://github.com/The-Compiler/qutebrowser/blob/master/tests/helpers/logfail.py > https://github.com/The-Compiler/qutebrowser/blob/master/tests/helpers/test_logfail.py I'm also checking stdout+stderr output, allow asserting that a log message is generated, and allow registering false positives. That makes the code a little more complicated, and thus it wouldn't be enough to just change pytest-catchlog. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F ?Time flies like an arrow, fruit flies like a Banana.? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 997 bytes Desc: not available URL: From raphael at hackebrot.de Sat Jun 11 11:13:54 2016 From: raphael at hackebrot.de (Raphael Pierzina) Date: Sat, 11 Jun 2016 16:13:54 +0100 Subject: [pytest-dev] CFP EuroPython 2016 Message-ID: <53653882-2CA8-4CBD-861E-B10689F6723E@hackebrot.de> Hi pytest-friends! The second CFP for EuroPython 2016 is open until tomorrow. It it reserved for ?hot? topics. I am thinking about speaking about the upcoming pytest developer sprint and what?s in store for pytest 3.0. What are your thoughts on this? Is anyone else keen to speak about this at EuroPython in July? Look forward to your feedback! Raphael -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Sun Jun 12 12:27:37 2016 From: flub at devork.be (Floris Bruynooghe) Date: Sun, 12 Jun 2016 17:27:37 +0100 Subject: [pytest-dev] CFP EuroPython 2016 In-Reply-To: <53653882-2CA8-4CBD-861E-B10689F6723E@hackebrot.de> References: <53653882-2CA8-4CBD-861E-B10689F6723E@hackebrot.de> Message-ID: Hi Raphael! On 11 June 2016 at 16:13, Raphael Pierzina wrote: > The second CFP for EuroPython 2016 is open until tomorrow. It it reserved > for ?hot? topics. I am thinking about speaking about the upcoming pytest > developer sprint and what?s in store for pytest 3.0. What are your thoughts > on this? Is anyone else keen to speak about this at EuroPython in July? Sure, this seems like it could be a nice talk. I'm sure everyone is fine with you submitting it! Floris From kvas.it at gmail.com Sun Jun 12 14:24:38 2016 From: kvas.it at gmail.com (Vasily Kuznetsov) Date: Sun, 12 Jun 2016 18:24:38 +0000 Subject: [pytest-dev] Testing of console scripts In-Reply-To: References: <20160428121108.GL18629@tonks> Message-ID: Hi Bruno, 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 Travis for reasons I didn't quite understand yet and the features, as well as documentation, are not complete, but I think it's enough to see the direction. Perhaps we could have a chat during the sprint if you have time. Thank you for the suggestion to use cookiecutter, that was quite helpful. Cheers, Vasily On Thu, Apr 28, 2016 at 9:52 PM Bruno Oliveira wrote: > 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 cookiecutter-pytest-plugin[1] to create the plugin > template for you. I can't stress enough how much time that saves you. :) > > [1] https://github.com/pytest-dev/cookiecutter-pytest-plugin > > Thanks, > Bruno. > >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Sun Jun 12 14:25:39 2016 From: me at the-compiler.org (Florian Bruhin) Date: Sun, 12 Jun 2016 20:25:39 +0200 Subject: [pytest-dev] CFP EuroPython 2016 In-Reply-To: References: <53653882-2CA8-4CBD-861E-B10689F6723E@hackebrot.de> Message-ID: <20160612182539.5rkowswry5sml7d7@tonks> * Floris Bruynooghe [2016-06-12 17:27:37 +0100]: > Hi Raphael! > > On 11 June 2016 at 16:13, Raphael Pierzina wrote: > > The second CFP for EuroPython 2016 is open until tomorrow. It it reserved > > for ?hot? topics. I am thinking about speaking about the upcoming pytest > > developer sprint and what?s in store for pytest 3.0. What are your thoughts > > on this? Is anyone else keen to speak about this at EuroPython in July? > > Sure, this seems like it could be a nice talk. I'm sure everyone is > fine with you submitting it! Note we might already have released 3.0 by then ;) I'd be happy to join with talking, but I'm not sure if it makes sense. Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From zimmermann.code at gmail.com Sun Jun 12 15:21:33 2016 From: zimmermann.code at gmail.com (Stefan Zimmermann) Date: Sun, 12 Jun 2016 19:21:33 +0000 Subject: [pytest-dev] Participation In-Reply-To: References: Message-ID: Hi. Following Ronny's advice I want to add some important information I just forgot in my previous mail: I want to arrive on 20th in the morning and depart at either 24th or 25th in the evening. I just can't make a certain decision on the latter yet. I also entered my travel and accommodation plans into the wiki. Stefan On Fri, Jun 10, 2016 at 8:36 PM Stefan Zimmermann wrote: > Hi Holger and all other members, > > I just want to tell that I'd also like to join the sprint. I hope it's not > too late. At least I don't need any funding. And will eat what's left ;) > > I'm working as Python/C++/Java developer at ADVA Optical Networking SE in > Meiningen, mainly related to RobotFramework-based test automation during > the last 5 years, now with different tasks... We use pytest for all of our > Python projects at work, and I do lots of open source development. So I > have just no reason for not joining :) > > I'm looking forward to see you all. > > Cheers, > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raphael at hackebrot.de Sun Jun 12 17:00:07 2016 From: raphael at hackebrot.de (Raphael Pierzina) Date: Sun, 12 Jun 2016 22:00:07 +0100 Subject: [pytest-dev] CFP EuroPython 2016 In-Reply-To: <20160612182539.5rkowswry5sml7d7@tonks> References: <53653882-2CA8-4CBD-861E-B10689F6723E@hackebrot.de> <20160612182539.5rkowswry5sml7d7@tonks> Message-ID: <52BC3BDA-FCE1-4B92-9B28-26BEB704091B@hackebrot.de> Hi, here?s my draft - I?d appreciate any last minute feedback! :) https://gist.github.com/hackebrot/4e18ec8912221585a3275e1f1fbd5a03 Cheers Raphael > On 12 Jun 2016, at 19:25, Florian Bruhin wrote: > > * Floris Bruynooghe [2016-06-12 17:27:37 +0100]: >> Hi Raphael! >> >> On 11 June 2016 at 16:13, Raphael Pierzina wrote: >>> The second CFP for EuroPython 2016 is open until tomorrow. It it reserved >>> for ?hot? topics. I am thinking about speaking about the upcoming pytest >>> developer sprint and what?s in store for pytest 3.0. What are your thoughts >>> on this? Is anyone else keen to speak about this at EuroPython in July? >> >> Sure, this seems like it could be a nice talk. I'm sure everyone is >> fine with you submitting it! > > Note we might already have released 3.0 by then ;) > I'd be happy to join with talking, but I'm not sure if it makes sense. > > Florian > > -- > http://www.the-compiler.org | me at 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/ > _______________________________________________ > 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 oliver at bestwalter.de Sun Jun 12 17:27:58 2016 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Sun, 12 Jun 2016 21:27:58 +0000 Subject: [pytest-dev] CFP EuroPython 2016 In-Reply-To: <52BC3BDA-FCE1-4B92-9B28-26BEB704091B@hackebrot.de> References: <53653882-2CA8-4CBD-861E-B10689F6723E@hackebrot.de> <20160612182539.5rkowswry5sml7d7@tonks> <52BC3BDA-FCE1-4B92-9B28-26BEB704091B@hackebrot.de> Message-ID: Hi Raphael, Abstract (longer version) -> is actually the short version and vice versa cheers Oliver On Sun, 12 Jun 2016 at 23:00 Raphael Pierzina wrote: > Hi, > > here?s my draft - I?d appreciate any last minute feedback! :) > > https://gist.github.com/hackebrot/4e18ec8912221585a3275e1f1fbd5a03 > > Cheers > Raphael > > On 12 Jun 2016, at 19:25, Florian Bruhin wrote: > > * Floris Bruynooghe [2016-06-12 17:27:37 +0100]: > > Hi Raphael! > > On 11 June 2016 at 16:13, Raphael Pierzina wrote: > > The second CFP for EuroPython 2016 is open until tomorrow. It it reserved > for ?hot? topics. I am thinking about speaking about the upcoming pytest > developer sprint and what?s in store for pytest 3.0. What are your thoughts > on this? Is anyone else keen to speak about this at EuroPython in July? > > > Sure, this seems like it could be a nice talk. I'm sure everyone is > fine with you submitting it! > > > Note we might already have released 3.0 by then ;) > I'd be happy to join with talking, but I'm not sure if it makes sense. > > Florian > > -- > http://www.the-compiler.org | me at 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/ > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raphael at hackebrot.de Sun Jun 12 18:13:14 2016 From: raphael at hackebrot.de (Raphael Pierzina) Date: Sun, 12 Jun 2016 23:13:14 +0100 Subject: [pytest-dev] CFP EuroPython 2016 In-Reply-To: References: <53653882-2CA8-4CBD-861E-B10689F6723E@hackebrot.de> <20160612182539.5rkowswry5sml7d7@tonks> <52BC3BDA-FCE1-4B92-9B28-26BEB704091B@hackebrot.de> Message-ID: Hi Oliver, thank you! You?re absolutely right. The long abstract exceeded the 1500 characters, so I had to revisit this part. Talk is submitted - wish me luck. Raphael > On 12 Jun 2016, at 22:27, Oliver Bestwalter wrote: > > Hi Raphael, > > Abstract (longer version) -> is actually the short version and vice versa > > cheers > Oliver > > On Sun, 12 Jun 2016 at 23:00 Raphael Pierzina > wrote: > Hi, > > here?s my draft - I?d appreciate any last minute feedback! :) > > https://gist.github.com/hackebrot/4e18ec8912221585a3275e1f1fbd5a03 > > Cheers > Raphael > >> On 12 Jun 2016, at 19:25, Florian Bruhin > wrote: >> >> * Floris Bruynooghe > [2016-06-12 17:27:37 +0100]: >>> Hi Raphael! >>> >>> On 11 June 2016 at 16:13, Raphael Pierzina > wrote: >>>> The second CFP for EuroPython 2016 is open until tomorrow. It it reserved >>>> for ?hot? topics. I am thinking about speaking about the upcoming pytest >>>> developer sprint and what?s in store for pytest 3.0. What are your thoughts >>>> on this? Is anyone else keen to speak about this at EuroPython in July? >>> >>> Sure, this seems like it could be a nice talk. I'm sure everyone is >>> fine with you submitting it! >> >> Note we might already have released 3.0 by then ;) >> I'd be happy to join with talking, but I'm not sure if it makes sense. >> >> Florian >> >> -- >> http://www.the-compiler.org | me at 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/ >> _______________________________________________ >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Mon Jun 13 13:36:36 2016 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 13 Jun 2016 17:36:36 +0000 Subject: [pytest-dev] Testing of console scripts In-Reply-To: References: <20160428121108.GL18629@tonks> Message-ID: 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 Travis for reasons I didn't quite understand yet and the > features, as well as documentation, are not complete, but I think it's > enough to see the direction. Perhaps we could have a chat during the sprint > if you have time. > Nice, well done! I would be glad to chat during the sprint, of course. Thank you for the suggestion to use cookiecutter, that was quite helpful. > No worries, thank Raphael as well for developing this excellent tool. :) Cheers, Bruno. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Mon Jun 13 17:37:17 2016 From: flub at devork.be (Floris Bruynooghe) Date: Mon, 13 Jun 2016 22:37:17 +0100 Subject: [pytest-dev] Climbing at the sprint Message-ID: Hello py.test sprinters, In the past some of us have been to the local climbing wall at conferences before. So I had a look and Freiburg seems to have 2 bouldering walls and a climbing wall. If anyone else expresses any interest I'd be happy to bring some climbing stuff and go climbing one or two evenings - if we're keen. According to 27crags.com there's even some outdoor places reachable by public transport that might work for the day off. But they're small and probably not worth the extra hassle and logistics of possibly splitting up activities. So, anyone else up for some climbing or bouldering one evening? Floris From kvas.it at gmail.com Mon Jun 13 18:55:01 2016 From: kvas.it at gmail.com (Vasily Kuznetsov) Date: Mon, 13 Jun 2016 22:55:01 +0000 Subject: [pytest-dev] Climbing at the sprint In-Reply-To: References: Message-ID: I'm definitely up for it. I can also bring the rope if it's worth it. Cheers, Vasily On Mon, Jun 13, 2016 at 11:34 PM Floris Bruynooghe wrote: > Hello py.test sprinters, > > In the past some of us have been to the local climbing wall at > conferences before. So I had a look and Freiburg seems to have 2 > bouldering walls and a climbing wall. If anyone else expresses any > interest I'd be happy to bring some climbing stuff and go climbing one > or two evenings - if we're keen. > > According to 27crags.com there's even some outdoor places reachable by > public transport that might work for the day off. But they're small > and probably not worth the extra hassle and logistics of possibly > splitting up activities. > > So, anyone else up for some climbing or bouldering one evening? > > Floris > _______________________________________________ > 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 andreas at pelme.se Tue Jun 14 01:07:07 2016 From: andreas at pelme.se (Andreas Pelme) Date: Tue, 14 Jun 2016 07:07:07 +0200 Subject: [pytest-dev] Climbing at the sprint In-Reply-To: References: Message-ID: <9D54E4BB-FF71-48E6-801E-009DE77DEDAC@pelme.se> I?m in! I?ll bring my shoes and harness! :) Cheers, Andreas > On 14 juni 2016, at 00:55, Vasily Kuznetsov wrote: > > I'm definitely up for it. I can also bring the rope if it's worth it. > > Cheers, > Vasily > > On Mon, Jun 13, 2016 at 11:34 PM Floris Bruynooghe wrote: > Hello py.test sprinters, > > In the past some of us have been to the local climbing wall at > conferences before. So I had a look and Freiburg seems to have 2 > bouldering walls and a climbing wall. If anyone else expresses any > interest I'd be happy to bring some climbing stuff and go climbing one > or two evenings - if we're keen. > > According to 27crags.com there's even some outdoor places reachable by > public transport that might work for the day off. But they're small > and probably not worth the extra hassle and logistics of possibly > splitting up activities. > > So, anyone else up for some climbing or bouldering one evening? > > Floris > _______________________________________________ > 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 me at the-compiler.org Tue Jun 14 03:27:54 2016 From: me at the-compiler.org (Florian Bruhin) Date: Tue, 14 Jun 2016 09:27:54 +0200 Subject: [pytest-dev] Sprint: GPG keysigning Message-ID: <20160614072754.m2owtrn2puxnqaj6@tonks> Hi, If you use GPG, I suggest we sign each other's keys at the sprint :) Since I'm guessing we're just a handful of people, I think it's easier if everyone brings fingerprint strips - you can generate them using gpg-key2ps (part of the signing-party project) if you're masochistic enough for the combination of Perl and Postscript (sorry!), or use something like http://keysheet.net/ - and of course a form of identification, but you should have that with you anyways ;) Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From me at the-compiler.org Tue Jun 14 03:17:54 2016 From: me at the-compiler.org (Florian Bruhin) Date: Tue, 14 Jun 2016 09:17:54 +0200 Subject: [pytest-dev] Climbing at the sprint In-Reply-To: References: Message-ID: <20160614071754.dbjxudt3mjggt7tr@tonks> * Floris Bruynooghe [2016-06-13 22:37:17 +0100]: > In the past some of us have been to the local climbing wall at > conferences before. So I had a look and Freiburg seems to have 2 > bouldering walls and a climbing wall. If anyone else expresses any > interest I'd be happy to bring some climbing stuff and go climbing one > or two evenings - if we're keen. > > According to 27crags.com there's even some outdoor places reachable by > public transport that might work for the day off. But they're small > and probably not worth the extra hassle and logistics of possibly > splitting up activities. > > So, anyone else up for some climbing or bouldering one evening? Is there something I can join without climbing experience and without being too much of a sports guy? If so, count me in, because it *does* sound like fun :P Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From andreas at pelme.se Tue Jun 14 03:32:04 2016 From: andreas at pelme.se (Andreas Pelme) Date: Tue, 14 Jun 2016 09:32:04 +0200 Subject: [pytest-dev] Climbing at the sprint In-Reply-To: <20160614071754.dbjxudt3mjggt7tr@tonks> References: <20160614071754.dbjxudt3mjggt7tr@tonks> Message-ID: > On 14 juni 2016, at 09:17, Florian Bruhin wrote: > > Is there something I can join without climbing experience and without > being too much of a sports guy? If so, count me in, because it *does* > sound like fun :P Yes for sure! It?s easy to get started and there are usually problems for all kinds of levels. You can most likely rent shoes/harness at the climbing gym. It is a lot of fun! :D Cheers, Andreas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail URL: From holger at merlinux.eu Tue Jun 14 04:54:25 2016 From: holger at merlinux.eu (Holger Krekel) Date: Tue, 14 Jun 2016 10:54:25 +0200 Subject: [pytest-dev] Sprint: GPG keysigning In-Reply-To: <20160614072754.m2owtrn2puxnqaj6@tonks> References: <20160614072754.m2owtrn2puxnqaj6@tonks> Message-ID: -- Sent using mobile touch keys, inducing, chances. On June 14, 2016 9:27:54 AM GMT+02:00, Florian Bruhin wrote: >Hi, > >If you use GPG, I suggest we sign each other's keys at the sprint :) Can do, but I am not fond of the passport thing and there are also practices of signing keys without that passport requirement. We could also use it to sign pytest, tox releases. Cheers holger >Since I'm guessing we're just a handful of people, I think it's easier >if everyone brings fingerprint strips - you can generate them using >gpg-key2ps (part of the signing-party project) if you're masochistic >enough for the combination of Perl and Postscript (sorry!), or use >something like http://keysheet.net/ - and of course a form of >identification, but you should have that with you anyways ;) > >Florian From flub at devork.be Tue Jun 14 05:50:17 2016 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 14 Jun 2016 10:50:17 +0100 Subject: [pytest-dev] Sprint: GPG keysigning In-Reply-To: References: <20160614072754.m2owtrn2puxnqaj6@tonks> Message-ID: On 14 June 2016 at 09:54, Holger Krekel wrote: > On June 14, 2016 9:27:54 AM GMT+02:00, Florian Bruhin wrote: >>Hi, >> >>If you use GPG, I suggest we sign each other's keys at the sprint :) > > Can do, but I am not fond of the passport thing and there are also practices > of signing keys without that passport requirement. We could also use it to > sign pytest, tox releases. I think this is a good idea as well. However I'm on Holger's side wrt government-issued IDs, I don't think they matter as I'm just interested in knowing the key belongs to you and not who you are according to your official (or forged!) ID. But I'm sure we can discuss the merits of this in plenty of detail next week :-) Floris From flub at devork.be Tue Jun 14 05:53:34 2016 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 14 Jun 2016 10:53:34 +0100 Subject: [pytest-dev] Climbing at the sprint In-Reply-To: References: <20160614071754.dbjxudt3mjggt7tr@tonks> Message-ID: On 14 June 2016 at 08:32, Andreas Pelme wrote: > >> On 14 juni 2016, at 09:17, Florian Bruhin wrote: >> >> Is there something I can join without climbing experience and without >> being too much of a sports guy? If so, count me in, because it *does* >> sound like fun :P > > Yes for sure! It?s easy to get started and there are usually problems for > all kinds of levels. You can most likely rent shoes/harness at the > climbing gym. It is a lot of fun! :D I'll confirm this, anyone with or without experience is free to join, climbing walls normally cater for all levels and can provide the gear. So we'll be more then happy to help anyone who wants to come along. Floris From omarkohl at gmail.com Tue Jun 14 12:33:08 2016 From: omarkohl at gmail.com (Omar Kohl) Date: Tue, 14 Jun 2016 18:33:08 +0200 Subject: [pytest-dev] Sprint: GPG keysigning In-Reply-To: References: <20160614072754.m2owtrn2puxnqaj6@tonks> Message-ID: <576031C4.3030909@gmail.com> Hi, I'm also interested in signing keys :-) See you soon! Omar On 14.06.2016 11:50, Floris Bruynooghe wrote: > On 14 June 2016 at 09:54, Holger Krekel wrote: >> On June 14, 2016 9:27:54 AM GMT+02:00, Florian Bruhin wrote: >>> Hi, >>> >>> If you use GPG, I suggest we sign each other's keys at the sprint :) >> >> Can do, but I am not fond of the passport thing and there are also practices >> of signing keys without that passport requirement. We could also use it to >> sign pytest, tox releases. > > I think this is a good idea as well. However I'm on Holger's side wrt > government-issued IDs, I don't think they matter as I'm just > interested in knowing the key belongs to you and not who you are > according to your official (or forged!) ID. But I'm sure we can > discuss the merits of this in plenty of detail next week :-) > > Floris > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From dhunt at mozilla.com Wed Jun 15 04:04:07 2016 From: dhunt at mozilla.com (Dave Hunt) Date: Wed, 15 Jun 2016 09:04:07 +0100 Subject: [pytest-dev] Climbing at the sprint In-Reply-To: References: <20160614071754.dbjxudt3mjggt7tr@tonks> Message-ID: <3419B6C4-D295-4209-ABBB-2119CF43CA4B@mozilla.com> I?m in, though the one and only time I?ve done indoor bouldering I cracked a rib. ;) Dave > On 14 Jun 2016, at 10:53, Floris Bruynooghe wrote: > > On 14 June 2016 at 08:32, Andreas Pelme wrote: >> >>> On 14 juni 2016, at 09:17, Florian Bruhin wrote: >>> >>> Is there something I can join without climbing experience and without >>> being too much of a sports guy? If so, count me in, because it *does* >>> sound like fun :P >> >> Yes for sure! It?s easy to get started and there are usually problems for >> all kinds of levels. You can most likely rent shoes/harness at the >> climbing gym. It is a lot of fun! :D > > I'll confirm this, anyone with or without experience is free to join, > climbing walls normally cater for all levels and can provide the gear. > So we'll be more then happy to help anyone who wants to come along. > > Floris > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From farmi at web.de Wed Jun 15 04:49:39 2016 From: farmi at web.de (Stefan Farmbauer) Date: Wed, 15 Jun 2016 08:49:39 +0000 Subject: [pytest-dev] Fwd: Climbing at the sprint In-Reply-To: References: <20160614071754.dbjxudt3mjggt7tr@tonks> <3419B6C4-D295-4209-ABBB-2119CF43CA4B@mozilla.com> Message-ID: ---------- Forwarded message --------- From: Stefan Farmbauer Date: Mi., 15. Juni 2016 10:49 Subject: Re: [pytest-dev] Climbing at the sprint To: Dave Hunt I'm in as well. Will be the first time after two years rest. I'm excited. See you Farmer Dave Hunt schrieb am Mi., 15. Juni 2016 10:04: > I?m in, though the one and only time I?ve done indoor bouldering I cracked > a rib. ;) > > Dave > > > On 14 Jun 2016, at 10:53, Floris Bruynooghe wrote: > > > > On 14 June 2016 at 08:32, Andreas Pelme wrote: > >> > >>> On 14 juni 2016, at 09:17, Florian Bruhin wrote: > >>> > >>> Is there something I can join without climbing experience and without > >>> being too much of a sports guy? If so, count me in, because it *does* > >>> sound like fun :P > >> > >> Yes for sure! It?s easy to get started and there are usually problems > for > >> all kinds of levels. You can most likely rent shoes/harness at the > >> climbing gym. It is a lot of fun! :D > > > > I'll confirm this, anyone with or without experience is free to join, > > climbing walls normally cater for all levels and can provide the gear. > > So we'll be more then happy to help anyone who wants to come along. > > > > Floris > > _______________________________________________ > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom at viner.tv Wed Jun 15 05:27:30 2016 From: tom at viner.tv (Tom Viner) Date: Wed, 15 Jun 2016 10:27:30 +0100 Subject: [pytest-dev] On-the-ground sprint communication Message-ID: Hi all, I'm arriving in Freiburg Saturday afternoon, and wondering how best to communicate for arranging meeting up and getting dinner / Sunday activities etc. Some app that makes my phone beep upon receiving a message would be handy :-) Signal or WhatsApp group chat? Something else? Looking forward to seeing everyone and some German cuisine! Cheers, Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Wed Jun 15 05:45:25 2016 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 15 Jun 2016 11:45:25 +0200 Subject: [pytest-dev] On-the-ground sprint communication In-Reply-To: References: Message-ID: <20160615094525.knodg5ujjge6lqxm@tonks> Hey Tom, * Tom Viner [2016-06-15 10:27:30 +0100]: > I'm arriving in Freiburg Saturday afternoon, and wondering how best to > communicate for arranging meeting up and getting dinner / Sunday activities > etc. > > Some app that makes my phone beep upon receiving a message would be handy > :-) > > Signal or WhatsApp group chat? Something else? For easier written communication at the sprint (i.e. with everyone there) I suggest IRC, because many already have that set up and it's the lowest common denominator. As for before that, I know Holger uses Signal, and I use Telegram and Threema as well. Or XMPP/IRC. Then again I probably won't find my German SIM card anyways so I won't have any internet connection ;) Florian -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From tom at viner.tv Wed Jun 15 07:59:30 2016 From: tom at viner.tv (Tom Viner) Date: Wed, 15 Jun 2016 12:59:30 +0100 Subject: [pytest-dev] On-the-ground sprint communication Message-ID: On 15 June 2016 at 10:45, wrote: > Date: Wed, 15 Jun 2016 11:45:25 +0200 > From: Florian Bruhin > > > Signal or WhatsApp group chat? Something else? > > For easier written communication at the sprint (i.e. with everyone > there) I suggest IRC, because many already have that set up and it's > the lowest common denominator. > > As for before that, I know Holger uses Signal, and I use Telegram and > Threema as well. Or XMPP/IRC. Then again I probably won't find my > German SIM card anyways so I won't have any internet connection ;) > > Florian > Ok, let's go with Signal then. I've put my number here: https://github.com/tomviner/pytest/wiki/On-the-ground-comms-for-sprint-2016 I'll tune into the irc too. -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Thu Jun 16 12:41:33 2016 From: holger at merlinux.eu (holger krekel) Date: Thu, 16 Jun 2016 18:41:33 +0200 Subject: [pytest-dev] sprint alias for latest sprint logistics Message-ID: <20160616164133.GG3381@uwanda> Hi all, as the sprint is gearing up, i've setup an alias sprint2016 at pytest dot org which has all the people attending. everyone can mail there. If you are attending but haven't received a mail in the last hour let me know personally. Accomodation should be sorted now, so let's hope for good weather soon -- up until sunday it's forecasted as a bit rainy, then better. best, holger From holger at merlinux.eu Sat Jun 25 04:16:23 2016 From: holger at merlinux.eu (holger krekel) Date: Sat, 25 Jun 2016 10:16:23 +0200 Subject: [pytest-dev] pytest-3.0 / tox-2.4 release plans Message-ID: <20160625081623.GQ4246@uwanda> hi from the pytest/tox sprint ... here is the current plan (keyword points) for getting pytest-3.0 and tox-2.4 finalized. It's WIP and we aim to complete as much as possible today. best. h. tox-conda/roadmap/development discussion: - (TBD) two pending PRs - (TBD) 2.4.0 relase (to be released end June) - (TBD) write doc draft for conda integration (hooks + ini) - (TBD) move to github pytest-3.0 discussion: - TO BE RELEASED BEFORE EUROPYTHON2016 -- between 11th and 14th definitely part of 3.0 - new --setup-only, --setup-plan options - (Steffen, Danielle, TBD) reporitng hooks for fixture setup/teardown - (DONE) new main entry point pytest (and py.test) - (TBD) remove py.test-X* entrypoints (with changelog entry) - (TBD) doc restructuring - (TBD) display pytest warnings by default (one line per warning) - (TBD) remove all deprecated command line options for 3.0 - (TBD) fixture conftest sharing / fixture namespace control, draft suggestion document - (TBD) merged fixtures becomes a doc draft (raphael, me) - (TBD) introduce deprecation docs based on oliver's sprint lightning talk - (TBD, Omar, Ted, Daniel) new option "--override-ini|-o ININAME=INIVALUE" to overrides ini values from the command line so that one can do e.g. "-o xfail_strict=True". We don't change the default. - (TBD) see about issuing a deprecation warning for yielding test functions - (TBD, Floris) remove reinterp assert maybe in 3.0: - (TBD) invocation-scope: e.g. monkeypatch and mocker would be useable from any scope. Will be marked experimental for 3.0. rather later than 3.0: - (rather later than 3.0) merge pytest-warnings module and route internal pytest warnings through python's warning system and integrate the pytest-warnings plugin into core (bruno, ronny will discuss) - holger/floris' original pycon work with "markdef" to introduce a markdef decorator to process all mark creations should go to 4.0 - yielding test functions: we could deprecate using setup state in yielding test functions so they can only be used for parametrization other issues: __multicall__: don't remove for 3.0 marks refactoring / PR merge (ronny, omar...) - ronny's refactoring should be closed and redone: - either first just move code - or do changes in mark.py - as to whitespace/flakes/pep warnings: do that while changing code anyway but no big pure whitespace/style changes xfail strict behaviour by default? not doing it for 3.0 - introduce xflaky in docs and as a synonmym for xfail(strict=False) (needs more discussion) From rvprasad at cis.ksu.edu Sat Jun 25 12:27:12 2016 From: rvprasad at cis.ksu.edu (Venkatesh Prasad Ranganath) Date: Sat, 25 Jun 2016 11:27:12 -0500 Subject: [pytest-dev] Request to bundle Pytest-finer-verdicts as a default plugin with pytest Message-ID: Hey All, What is the process to make this happen? Is the first step to transfer pytest-finer-verdicts to pytest-dev organization? If so, please consider this email as the request for transfer. Cheers, Venkatesh-Prasad Ranganath http://about.me/rvprasad -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Sat Jun 25 17:05:27 2016 From: me at the-compiler.org (Florian Bruhin) Date: Sat, 25 Jun 2016 23:05:27 +0200 Subject: [pytest-dev] Request to bundle Pytest-finer-verdicts as a default plugin with pytest In-Reply-To: References: Message-ID: <20160625210527.pccputypuapeppuh@tonks> * Venkatesh Prasad Ranganath [2016-06-25 11:27:12 -0500]: > What is the process to make this happen? Is the first step to transfer > pytest-finer-verdicts to > pytest-dev organization? If so, please consider this email as the request > for transfer. Transfering sounds like a good idea, though you don't follow the requirements from [1] yet (having a tox.ini and long description in setup.py). Changing the default behaviour of what failure/error means seems like a bad idea, both from the perspective of people's exceptions and the backwards compatibility break it'll be. Florian [1] http://pytest.org/latest/contributing.html#submitting-plugins-to-pytest-dev -- http://www.the-compiler.org | me at 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From rvprasad at cis.ksu.edu Sun Jun 26 12:54:34 2016 From: rvprasad at cis.ksu.edu (Venkatesh Prasad Ranganath) Date: Sun, 26 Jun 2016 11:54:34 -0500 Subject: [pytest-dev] Request to bundle Pytest-finer-verdicts as a default plugin with pytest In-Reply-To: References: Message-ID: Hey Florian, I can look into tox.ini and longer description in setup.py. As for changed behavior, would providing a CLI option to activate the plugin suffice? Venkatesh-Prasad Ranganath http://about.me/rvprasad On Sat, Jun 25, 2016 at 11:27 AM, Venkatesh Prasad Ranganath < rvprasad at cis.ksu.edu> wrote: > Hey All, > > What is the process to make this happen? Is the first step to transfer > pytest-finer-verdicts to > pytest-dev organization? If so, please consider this email as the request > for transfer. > > Cheers, > > Venkatesh-Prasad Ranganath > http://about.me/rvprasad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Mon Jun 27 04:21:18 2016 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Mon, 27 Jun 2016 10:21:18 +0200 Subject: [pytest-dev] Request to bundle Pytest-finer-verdicts as a default plugin with pytest In-Reply-To: References: Message-ID: <7a150e56-46bf-3738-e257-d2045dbeffd1@ronnypfannschmidt.de> Hello Venkatesh-Prasad and Florian, as of now the linked plugin is basically a really new plugin, which is a 20 line function without any tests. as such i would like to postpone moving it into pytest-dev until it is more widely used and has a proper test-suite. we want to have pytest-dev as a place to put popular plugins in order to ease and open up maintenance and share control, we might want to have a different place for the public/shared incubation of plugins and experiments. -- Ronny Am 26.06.2016 um 18:54 schrieb Venkatesh Prasad Ranganath: > Hey Florian, > > I can look into tox.ini and longer description in setup.py. > > As for changed behavior, would providing a CLI option to activate the > plugin suffice? > > Venkatesh-Prasad Ranganath > http://about.me/rvprasad > > On Sat, Jun 25, 2016 at 11:27 AM, Venkatesh Prasad Ranganath > > wrote: > > Hey All, > > What is the process to make this happen? Is the first step to > transfer pytest-finer-verdicts > to pytest-dev > organization? If so, please consider this email as the request > for transfer. > > Cheers, > > Venkatesh-Prasad Ranganath > http://about.me/rvprasad > > > > > _______________________________________________ > 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 holger at merlinux.eu Mon Jun 27 10:20:33 2016 From: holger at merlinux.eu (holger krekel) Date: Mon, 27 Jun 2016 16:20:33 +0200 Subject: [pytest-dev] Request to bundle Pytest-finer-verdicts as a default plugin with pytest In-Reply-To: <7a150e56-46bf-3738-e257-d2045dbeffd1@ronnypfannschmidt.de> References: <7a150e56-46bf-3738-e257-d2045dbeffd1@ronnypfannschmidt.de> Message-ID: <20160627142033.GG4246@uwanda> On Mon, Jun 27, 2016 at 10:21 +0200, Ronny Pfannschmidt wrote: > Hello Venkatesh-Prasad and Florian, > > as of now the linked plugin is basically a really new plugin, which is a > 20 line function without any tests. > as such i would like to postpone moving it into pytest-dev until it is > more widely used and has a proper test-suite. > > we want to have pytest-dev as a place to put popular plugins in order to > ease and open up maintenance and share control, > we might want to have a different place for the public/shared incubation > of plugins and experiments. > -- Ronny I see it similarly. Also, i'd like to note that in my view submitting a plugin to pytest-dev does not imply that it will be maintained by "others" from then on. Rather contributing a plugin usually means continuing to care for it and collaborating on pytest core issues and, as ronny mentions, sharing commit and release control to reduce bus factors etc. holger > > > Am 26.06.2016 um 18:54 schrieb Venkatesh Prasad Ranganath: > > Hey Florian, > > > > I can look into tox.ini and longer description in setup.py. > > > > As for changed behavior, would providing a CLI option to activate the > > plugin suffice? > > > > Venkatesh-Prasad Ranganath > > http://about.me/rvprasad > > > > On Sat, Jun 25, 2016 at 11:27 AM, Venkatesh Prasad Ranganath > > > wrote: > > > > Hey All, > > > > What is the process to make this happen? Is the first step to > > transfer pytest-finer-verdicts > > to pytest-dev > > organization? If so, please consider this email as the request > > for transfer. > > > > Cheers, > > > > Venkatesh-Prasad Ranganath > > http://about.me/rvprasad > > > > > > > > > > _______________________________________________ > > 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 rvprasad at cis.ksu.edu Mon Jun 27 12:22:43 2016 From: rvprasad at cis.ksu.edu (Venkatesh Prasad Ranganath) Date: Mon, 27 Jun 2016 11:22:43 -0500 Subject: [pytest-dev] Request to bundle Pytest-finer-verdicts as a default plugin with pytest In-Reply-To: <20160627142033.GG4246@uwanda> References: <7a150e56-46bf-3738-e257-d2045dbeffd1@ronnypfannschmidt.de> <20160627142033.GG4246@uwanda> Message-ID: Hey All, I appreciate the inputs. A couple of clarifications. - I developed the plugin based on my experience with nosetest and pytest while teaching a software testing course. I plan to use it in the future editions of the course. For this purpose, the plugin suffices in its current form -- features and distribution. - The intention to move to pytest-dev is not to off load maintenance. I plan to maintain the plugin. [It is so simple :)] - Since verdicts are core of xunit frameworks, I figured having pytest-finer-verdicts as a default plugin might be useful to others; even if it needs to enabled explicitly (via CLI options). - IIRC, the plugin is really four lines of modification to pytest_runtest_makereport function in pytest. It was set up this way as this was the best way (I could figure out) to inject the desired functionality into pytest. All said, I am fine to wait for wider adoption of the plugin before we integrate it into pytest. I am fine if we want leave it as non-default plugin. I understand and respect these decisions. So, for now, I'll shelf this issue (and withdraw my request) until there is interest from the community. Cheers, Venkatesh-Prasad Ranganath http://about.me/rvprasad On Mon, Jun 27, 2016 at 9:20 AM, holger krekel wrote: > On Mon, Jun 27, 2016 at 10:21 +0200, Ronny Pfannschmidt wrote: > > Hello Venkatesh-Prasad and Florian, > > > > as of now the linked plugin is basically a really new plugin, which is a > > 20 line function without any tests. > > as such i would like to postpone moving it into pytest-dev until it is > > more widely used and has a proper test-suite. > > > > we want to have pytest-dev as a place to put popular plugins in order to > > ease and open up maintenance and share control, > > we might want to have a different place for the public/shared incubation > > of plugins and experiments. > > -- Ronny > > I see it similarly. Also, i'd like to note that in my view submitting a > plugin to pytest-dev does not imply that it will be maintained by > "others" from then on. Rather contributing a plugin usually means > continuing to care for it and collaborating on pytest core issues and, as > ronny > mentions, sharing commit and release control to reduce bus factors etc. > > holger > > > > > > > Am 26.06.2016 um 18:54 schrieb Venkatesh Prasad Ranganath: > > > Hey Florian, > > > > > > I can look into tox.ini and longer description in setup.py. > > > > > > As for changed behavior, would providing a CLI option to activate the > > > plugin suffice? > > > > > > Venkatesh-Prasad Ranganath > > > http://about.me/rvprasad > > > > > > On Sat, Jun 25, 2016 at 11:27 AM, Venkatesh Prasad Ranganath > > > > wrote: > > > > > > Hey All, > > > > > > What is the process to make this happen? Is the first step to > > > transfer pytest-finer-verdicts > > > to pytest-dev > > > organization? If so, please consider this email as the request > > > for transfer. > > > > > > Cheers, > > > > > > Venkatesh-Prasad Ranganath > > > http://about.me/rvprasad > > > > > > > > > > > > > > > _______________________________________________ > > > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhunt at mozilla.com Tue Jun 28 08:30:46 2016 From: dhunt at mozilla.com (Dave Hunt) Date: Tue, 28 Jun 2016 13:30:46 +0100 Subject: [pytest-dev] Request for additional plugin maintainers on PyPI Message-ID: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> Last week the following plugins of mine were moved into pytest-dev: https://github.com/pytest-dev/pytest-selenium https://github.com/pytest-dev/pytest-html https://github.com/pytest-dev/pytest-variables https://github.com/pytest-dev/pytest-base-url I fully intend to continue to support these plugins myself. The main reason for moving these is to ensure that patches for important fixes can be made without me. I?d also like to add at least one maintainer for each of these projects in PyPI so that releases can be pushed without me. Please respond with your GitHub username if you would like to be added as a developer for any of the above plugins, and your PyPI username if you would like to be considered as a maintainer (so you can push new releases). At this time I would like to restrict new developers and maintainers to pytest core committers. Thanks, -- Dave Hunt Automation Engineer Mozilla Corporation dhunt at mozilla.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpfannsc at redhat.com Tue Jun 28 09:01:32 2016 From: rpfannsc at redhat.com (Ronny Pfannschmidt) Date: Tue, 28 Jun 2016 15:01:32 +0200 Subject: [pytest-dev] Request for additional plugin maintainers on PyPI In-Reply-To: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> References: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> Message-ID: Hi dave, i would like to suggest to just give the pytest core group pr merge access, -- Ronny 2016-06-28 14:30 GMT+02:00 Dave Hunt : > Last week the following plugins of mine were moved into pytest-dev: > > - https://github.com/pytest-dev/pytest-selenium > - https://github.com/pytest-dev/pytest-html > - https://github.com/pytest-dev/pytest-variables > - https://github.com/pytest-dev/pytest-base-url > > I fully intend to continue to support these plugins myself. The main > reason for moving these is to ensure that patches for important fixes can > be made without me. I?d also like to add at least one maintainer for each > of these projects in PyPI so that releases can be pushed without me. > > Please respond with your GitHub username if you would like to be added as > a developer for any of the above plugins, and your PyPI username if you > would like to be considered as a maintainer (so you can push new releases). > At this time I would like to restrict new developers and maintainers to > pytest core committers. > > Thanks, > > -- > *Dave Hunt* > Automation Engineer > Mozilla Corporation > dhunt at mozilla.com > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhunt at mozilla.com Tue Jun 28 09:05:15 2016 From: dhunt at mozilla.com (Dave Hunt) Date: Tue, 28 Jun 2016 14:05:15 +0100 Subject: [pytest-dev] Request for additional plugin maintainers on PyPI In-Reply-To: References: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> Message-ID: <48B13BAD-0501-4D6E-8E88-DFB882B7D005@mozilla.com> Good idea - done! I?ll still need at least one maintainer for each plugin in PyPI. > On 28 Jun 2016, at 14:01, Ronny Pfannschmidt wrote: > > Hi dave, > > i would like to suggest to just give the pytest core group pr merge access, > > -- Ronny > > 2016-06-28 14:30 GMT+02:00 Dave Hunt >: > Last week the following plugins of mine were moved into pytest-dev: > https://github.com/pytest-dev/pytest-selenium > https://github.com/pytest-dev/pytest-html > https://github.com/pytest-dev/pytest-variables > https://github.com/pytest-dev/pytest-base-url > I fully intend to continue to support these plugins myself. The main reason for moving these is to ensure that patches for important fixes can be made without me. I?d also like to add at least one maintainer for each of these projects in PyPI so that releases can be pushed without me. > > Please respond with your GitHub username if you would like to be added as a developer for any of the above plugins, and your PyPI username if you would like to be considered as a maintainer (so you can push new releases). At this time I would like to restrict new developers and maintainers to pytest core committers. > > Thanks, > > -- > Dave Hunt > Automation Engineer > Mozilla Corporation > dhunt at mozilla.com > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > -- > Red Hat GmbH, http://www.de.redhat.com/ , Registered seat: Grasbrunn, > Commercial register: Amtsgericht Muenchen, HRB 153243, > Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Tue Jun 28 09:14:12 2016 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 28 Jun 2016 15:14:12 +0200 Subject: [pytest-dev] Request for additional plugin maintainers on PyPI In-Reply-To: <48B13BAD-0501-4D6E-8E88-DFB882B7D005@mozilla.com> References: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> <48B13BAD-0501-4D6E-8E88-DFB882B7D005@mozilla.com> Message-ID: Sadly pypi does not have groups so not as easy. My username is flub there, probably want to add a few pytest-dev ppl other then me as well tough On 28 Jun 2016 15:05, "Dave Hunt" wrote: > Good idea - done! I?ll still need at least one maintainer for each plugin > in PyPI. > > On 28 Jun 2016, at 14:01, Ronny Pfannschmidt wrote: > > Hi dave, > > i would like to suggest to just give the pytest core group pr merge access, > > -- Ronny > > 2016-06-28 14:30 GMT+02:00 Dave Hunt : > >> Last week the following plugins of mine were moved into pytest-dev: >> >> - https://github.com/pytest-dev/pytest-selenium >> - https://github.com/pytest-dev/pytest-html >> - https://github.com/pytest-dev/pytest-variables >> - https://github.com/pytest-dev/pytest-base-url >> >> I fully intend to continue to support these plugins myself. The main >> reason for moving these is to ensure that patches for important fixes can >> be made without me. I?d also like to add at least one maintainer for each >> of these projects in PyPI so that releases can be pushed without me. >> >> Please respond with your GitHub username if you would like to be added as >> a developer for any of the above plugins, and your PyPI username if you >> would like to be considered as a maintainer (so you can push new releases). >> At this time I would like to restrict new developers and maintainers to >> pytest core committers. >> >> Thanks, >> >> -- >> *Dave Hunt* >> Automation Engineer >> Mozilla Corporation >> dhunt at mozilla.com >> >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> >> > > > -- > > Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, > Commercial register: Amtsgericht Muenchen, HRB 153243, > Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander > > > > _______________________________________________ > 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 rpfannsc at redhat.com Tue Jun 28 09:13:35 2016 From: rpfannsc at redhat.com (Ronny Pfannschmidt) Date: Tue, 28 Jun 2016 15:13:35 +0200 Subject: [pytest-dev] Request for additional plugin maintainers on PyPI In-Reply-To: <48B13BAD-0501-4D6E-8E88-DFB882B7D005@mozilla.com> References: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> <48B13BAD-0501-4D6E-8E88-DFB882B7D005@mozilla.com> Message-ID: i wonder if we should start to create a setup, where a deploy hook does pypi uploads on tagged commits, then all pytest-dev plugins could be automated 2016-06-28 15:05 GMT+02:00 Dave Hunt : > Good idea - done! I?ll still need at least one maintainer for each plugin > in PyPI. > > On 28 Jun 2016, at 14:01, Ronny Pfannschmidt wrote: > > Hi dave, > > i would like to suggest to just give the pytest core group pr merge access, > > -- Ronny > > 2016-06-28 14:30 GMT+02:00 Dave Hunt : > >> Last week the following plugins of mine were moved into pytest-dev: >> >> - https://github.com/pytest-dev/pytest-selenium >> - https://github.com/pytest-dev/pytest-html >> - https://github.com/pytest-dev/pytest-variables >> - https://github.com/pytest-dev/pytest-base-url >> >> I fully intend to continue to support these plugins myself. The main >> reason for moving these is to ensure that patches for important fixes can >> be made without me. I?d also like to add at least one maintainer for each >> of these projects in PyPI so that releases can be pushed without me. >> >> Please respond with your GitHub username if you would like to be added as >> a developer for any of the above plugins, and your PyPI username if you >> would like to be considered as a maintainer (so you can push new releases). >> At this time I would like to restrict new developers and maintainers to >> pytest core committers. >> >> Thanks, >> >> -- >> *Dave Hunt* >> Automation Engineer >> Mozilla Corporation >> dhunt at mozilla.com >> >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> >> > > > -- > > Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, > Commercial register: Amtsgericht Muenchen, HRB 153243, > Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander > > > -- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpfannsc at redhat.com Tue Jun 28 09:48:07 2016 From: rpfannsc at redhat.com (Ronny Pfannschmidt) Date: Tue, 28 Jun 2016 15:48:07 +0200 Subject: [pytest-dev] Request for additional plugin maintainers on PyPI In-Reply-To: References: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> <48B13BAD-0501-4D6E-8E88-DFB882B7D005@mozilla.com> Message-ID: if we have a "dedicated" pytest-dev user, and put the password into a travis encrypted field, thing might be reasonably fine 2016-06-28 15:14 GMT+02:00 Floris Bruynooghe : > Sadly pypi does not have groups so not as easy. My username is flub there, > probably want to add a few pytest-dev ppl other then me as well tough > On 28 Jun 2016 15:05, "Dave Hunt" wrote: > >> Good idea - done! I?ll still need at least one maintainer for each plugin >> in PyPI. >> >> On 28 Jun 2016, at 14:01, Ronny Pfannschmidt wrote: >> >> Hi dave, >> >> i would like to suggest to just give the pytest core group pr merge >> access, >> >> -- Ronny >> >> 2016-06-28 14:30 GMT+02:00 Dave Hunt : >> >>> Last week the following plugins of mine were moved into pytest-dev: >>> >>> - https://github.com/pytest-dev/pytest-selenium >>> - https://github.com/pytest-dev/pytest-html >>> - https://github.com/pytest-dev/pytest-variables >>> - https://github.com/pytest-dev/pytest-base-url >>> >>> I fully intend to continue to support these plugins myself. The main >>> reason for moving these is to ensure that patches for important fixes can >>> be made without me. I?d also like to add at least one maintainer for each >>> of these projects in PyPI so that releases can be pushed without me. >>> >>> Please respond with your GitHub username if you would like to be added >>> as a developer for any of the above plugins, and your PyPI username if you >>> would like to be considered as a maintainer (so you can push new releases). >>> At this time I would like to restrict new developers and maintainers to >>> pytest core committers. >>> >>> Thanks, >>> >>> -- >>> *Dave Hunt* >>> Automation Engineer >>> Mozilla Corporation >>> dhunt at mozilla.com >>> >>> >>> _______________________________________________ >>> pytest-dev mailing list >>> pytest-dev at python.org >>> https://mail.python.org/mailman/listinfo/pytest-dev >>> >>> >> >> >> -- >> >> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, >> Commercial register: Amtsgericht Muenchen, HRB 153243, >> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander >> >> >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> >> -- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianna.laugher at gmail.com Tue Jun 28 10:34:33 2016 From: brianna.laugher at gmail.com (Brianna Laugher) Date: Wed, 29 Jun 2016 00:34:33 +1000 Subject: [pytest-dev] readthedocs building? Message-ID: Hi, Since this got merged https://github.com/pytest-dev/pytest/pull/1656 but http://pytest.readthedocs.io/en/latest/ still shows the fundraising banner... does anyone know why? I thought it built a new version on each commit. Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Tue Jun 28 11:32:44 2016 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Tue, 28 Jun 2016 15:32:44 +0000 Subject: [pytest-dev] readthedocs building? In-Reply-To: References: Message-ID: 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 -> last release (also redirected from /). I explicitly asked for a new latest build, and now the banner is gone. As to why latest wasn?t already up to date I don?t know? according to the docs, it should already be updated any time commits to master are added. Well, let?s see how it behaves now that I explicitly set ?Default Branch? to master. Cheers, Bruno. ? On Tue, Jun 28, 2016 at 11:34 AM Brianna Laugher wrote: > Hi, > > Since this got merged > https://github.com/pytest-dev/pytest/pull/1656 > > but http://pytest.readthedocs.io/en/latest/ still shows the fundraising > banner... does anyone know why? I thought it built a new version on each > commit. > > Brianna > > > -- > They've just been waiting in a mountain for the right moment: > http://modernthings.org/ > _______________________________________________ > 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 Tue Jun 28 12:14:38 2016 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 28 Jun 2016 18:14:38 +0200 Subject: [pytest-dev] Request for additional plugin maintainers on PyPI In-Reply-To: References: <05A0CC05-245D-4202-B406-44F92456ED35@mozilla.com> <48B13BAD-0501-4D6E-8E88-DFB882B7D005@mozilla.com> Message-ID: Oops, lost the pytest-dev cc. Apologies On 28 Jun 2016 18:13, "Ronny Pfannschmidt" wrote: > I'd be happy to have that, but Travis is very limited just as our > resources are > Am 28.06.2016 18:04 schrieb "Floris Bruynooghe" : > >> Sounds nice, I'm all for more automation! But should devpi not be >> involved somehow? >> On 28 Jun 2016 15:48, "Ronny Pfannschmidt" wrote: >> >>> if we have a "dedicated" pytest-dev user, and put the password into a >>> travis encrypted field, thing might be reasonably fine >>> >>> >>> >>> 2016-06-28 15:14 GMT+02:00 Floris Bruynooghe : >>> >>>> Sadly pypi does not have groups so not as easy. My username is flub >>>> there, probably want to add a few pytest-dev ppl other then me as well tough >>>> On 28 Jun 2016 15:05, "Dave Hunt" wrote: >>>> >>>>> Good idea - done! I?ll still need at least one maintainer for each >>>>> plugin in PyPI. >>>>> >>>>> On 28 Jun 2016, at 14:01, Ronny Pfannschmidt >>>>> wrote: >>>>> >>>>> Hi dave, >>>>> >>>>> i would like to suggest to just give the pytest core group pr merge >>>>> access, >>>>> >>>>> -- Ronny >>>>> >>>>> 2016-06-28 14:30 GMT+02:00 Dave Hunt : >>>>> >>>>>> Last week the following plugins of mine were moved into pytest-dev: >>>>>> >>>>>> - https://github.com/pytest-dev/pytest-selenium >>>>>> - https://github.com/pytest-dev/pytest-html >>>>>> - https://github.com/pytest-dev/pytest-variables >>>>>> - https://github.com/pytest-dev/pytest-base-url >>>>>> >>>>>> I fully intend to continue to support these plugins myself. The main >>>>>> reason for moving these is to ensure that patches for important fixes can >>>>>> be made without me. I?d also like to add at least one maintainer for each >>>>>> of these projects in PyPI so that releases can be pushed without me. >>>>>> >>>>>> Please respond with your GitHub username if you would like to be >>>>>> added as a developer for any of the above plugins, and your PyPI username >>>>>> if you would like to be considered as a maintainer (so you can push new >>>>>> releases). At this time I would like to restrict new developers and >>>>>> maintainers to pytest core committers. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> -- >>>>>> *Dave Hunt* >>>>>> Automation Engineer >>>>>> Mozilla Corporation >>>>>> dhunt at mozilla.com >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> pytest-dev mailing list >>>>>> pytest-dev at python.org >>>>>> https://mail.python.org/mailman/listinfo/pytest-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, >>>>> Commercial register: Amtsgericht Muenchen, HRB 153243, >>>>> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> pytest-dev mailing list >>>>> pytest-dev at python.org >>>>> https://mail.python.org/mailman/listinfo/pytest-dev >>>>> >>>>> >>> >>> >>> -- >>> >>> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, >>> Commercial register: Amtsgericht Muenchen, HRB 153243, >>> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver at bestwalter.de Wed Jun 29 13:16:11 2016 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Wed, 29 Jun 2016 17:16:11 +0000 Subject: [pytest-dev] pytest 3.0 release check list Message-ID: Hi all, I created a wiki page containing the checklist for the 3.0 release that resulted from our discussion during the sprint. https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist I think that is better than opening an issue, because everybody involved can update the page directly and if there is still some discussion necessary regarding concrete topics an issue can be opened for that concrete topic. cheers Oliver -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Wed Jun 29 15:04:01 2016 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 29 Jun 2016 19:04:01 +0000 Subject: [pytest-dev] pytest 3.0 release check list In-Reply-To: References: Message-ID: 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 wrote: > Hi all, > > I created a wiki page containing the checklist for the 3.0 release that > resulted from our discussion during the sprint. > > https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist > > I think that is better than opening an issue, because everybody involved > can update the page directly and if there is still some discussion > necessary regarding concrete topics an issue can be opened for that > concrete topic. > > cheers > Oliver > _______________________________________________ > 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: