[pytest-dev] pytest development sprint 2024

Hey! [Cross-posted from GitHub discussions for visibility] I'm happy to announce that in collaboration with OMICRON[1], I'm aiming to organize another pytest development sprint in 2024! Back in 2016, we had an amazing[2] development sprint in Freiburg, Germany, with a successful crowdfunding[3]

Re: [pytest-dev] New plugin - pytest-pyspec

Hey Felipe, On Sat, Mar 11, 2023 at 05:58:49PM -0300, Felipe Curty wrote: > I am glad to announce that I created my first plugin in pytest and it is > ready for use. It is called pytest-pyspec ( > https://pypi.org/project/pytest-pyspec). Congrats on the release! > I would like to list it in the

Re: [pytest-dev] Enabling 2FA for pytest-dev on PyPI

Hey, On Mon, Jan 23, 2023 at 09:56:14PM +0100, Floris Bruynooghe wrote: > The tidelift message seems to be because they don't have the information > from pypi, which is fair enough. So they require you to login to > tidelift and tick a box saying "I've enabled 2FA on PyPI". Which > TheCompiler h

[pytest-dev] pytest 7.0.0 released

Sottile * Ben Davies * Bernát Gábor * Brian Okken * Bruno Oliveira * Cristian Vera * Dan Alvizu * David Szotten * Eddie * Emmanuel Arias * Emmanuel Meric de Bellefon * Eric Liu * Florian Bruhin * GergelyKalmar * Graeme Smecher * Harshna * Hugo van Kemenade * Jakub Kulík * James Myatt * Jeff Rasley

[pytest-dev] pytest 7.0.0rc1 released!

* Cristian Vera * David Szotten * Eddie * Emmanuel Arias * Emmanuel Meric de Bellefon * Eric Liu * Florian Bruhin * GergelyKalmar * Graeme Smecher * Harshna * Hugo van Kemenade * Jakub Kulík * James Myatt * Jeff Rasley * Kale Kundert * Miro Hrončok * Naveen-Pratap * Oleg Höfling * Ran Benita * Ronny

[pytest-dev] Digging into pytest's history

Hey, I'm not sure how many of you follow GitHub Discussions in the pytest-dev repository, so I'm crossposting this (lightly edited) from there: https://github.com/pytest-dev/pytest/discussions/8667 I've always wondered when pytest actually really was born - the first commit in the current pytest

Re: [pytest-dev] Testing fixture teardown / finalisation

Hey, On Wed, Jan 06, 2021 at 03:26:08PM -0300, Bruno Oliveira wrote: > What I suggest you do in your case is to decouple your code from the > fixture, so if you have something like this today: > > [setup / teardown in a fixture] > > You can write instead: > > @contextmanager > def h

Re: [pytest-dev] Do we have a place to introduce new plugins.

Hey, On Wed, Nov 18, 2020 at 11:15:02AM +0300, Arseniy Antonov wrote: > Hi all, > I think it would be great to have a single place like for example reddit or > something like that where anyone could be able to introduce and discuss new > plugins or ask the community for support. > Mailing lists qu

Re: [pytest-dev] Transfer of pytest-html and pytest-molecule under pytest-dev

On Mon, Aug 17, 2020 at 04:54:20PM -0300, Bruno Oliveira wrote: > On Mon, Aug 17, 2020 at 4:42 PM Floris Bruynooghe wrote: > > > On Mon 17 Aug 2020 at 08:51 -0300, Bruno Oliveira wrote: > > > On Sat, Aug 15, 2020 at 2:05 PM Sorin Sbarnea > > wrote: > > >> https://pypi.org/project/pytest-plus/ >

[pytest-dev] Webinar and training about pytest basics (German / Switzerland)

Hey, (Back in June, I've sent a mail about a pytest workshop I'm giving in September. I'm not sure if it made it through everywhere, as I accidentally used a mail address which wasn't subscribed to the lists I was posting to. Since I also have a second announcement to make, I'm taking the freedom

Re: [pytest-dev] Test discovery

Hey Rob, On Sat, Aug 01, 2020 at 11:16:52PM -0700, Rob McDonald wrote: > According to Google, 'How does pytest discover tests' is an oft-asked > question. However most of those questions actually want to know 'What > criteria does pytest use to discover tests'... > > I'm working on a program tha

Re: [pytest-dev] maintenance of pytest-html

On Wed, Jul 29, 2020 at 03:32:16PM +0100, Sorin Sbarnea wrote: > CI/CD is cheap, human work is expensive. > > If you avoid testing it PR, you will allow introduction of changes that break > the master branch. > > For small projects it does not make sense to avoid testing anything before > merge (

Re: [pytest-dev] maintenance of pytest-html

On Wed, Jul 29, 2020 at 02:59:24PM +0100, Thomas Grainger wrote: > > Why? Something like a tox environment running against the latest pytest > > prerelease (or pytest master even) plus a scheduled build job should totally > > suffice, no? > > -1 on depending on unpined deps in CI this causes the d

Re: [pytest-dev] maintenance of pytest-html

Hey everyone, There are various things in this thread I want to answer to, so I'll just answer to three mails in one :) On Wed, Jul 29, 2020 at 10:43:21AM +0100, Sorin Sbarnea wrote: > There was nothing wrong with pytest release process, there was a pre-release > and also enough time to raise bug

[pytest-dev] [ANN] Open pytest training (German) at the CH Open Workshoptage, September 2020, Switzerland

Hey, Just a quick announcement that I plan to give a full-day hands-on pytest training in September in Switzerland (slides in English, but the training will be in German): https://workshoptage.ch/workshops/2020/pytest-test-driven-development-nicht-nur-fuer-python/ The training is a part of the "W

Re: [pytest-dev] Pytest-stress Maintainers

Hey Imran, On Thu, Apr 30, 2020 at 10:58:30PM -0700, Imran M wrote: > Would any of the pytest-stress maintainers check out the issues page when > they get a chance please? > > https://github.com/pytest-dev/pytest-metadata/issues pytest-stress or pytest-metadata? Florian -- m...@the-compiler.o

Re: [pytest-dev] How to duplicate pytest.Item inside function 'pytest_collection_modifyitems'?

Hey, On Wed, Apr 15, 2020 at 03:16:45AM +0530, Anton Shiban wrote: > Can you please guide me *how to* *clone pytest.Item?* > > I want to take one *item* from *items* array (inside function > ‘pytest_collection_modifyitems’) and clone that *item* and add it to *items* > array back. > > Can someon

Re: [pytest-dev] [RFC] experimenting with using matrix as chat/community platform for potentially superseding irc

Hey Ronny, hey everyone, On Sat, Feb 08, 2020 at 02:39:54PM +0100, Ronny Pfannschmidt wrote: > since a while now i have stopped using irc directly/controlled and > instead switched to a setup using matrix that i like much better. > > Matrix enables a few features that i really like, for example >

Re: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching

Hey, On Wed, Dec 04, 2019 at 10:58:09AM -0300, Bruno Oliveira wrote: > I would actually vote to change the existing behavior to be > case-insensitive. I doubt it would break many suites, if at all, and would > be more in alignment with the intent of the option, more of it being a > "partial match"

Re: [pytest-dev] Plugin Submission "pytest-stress "

Hey Imran, On Sat, Nov 16, 2019 at 06:48:33PM -0800, Imran M wrote: > I would like to submit this plugin: > > https://github.com/ImXron/pytest-stress > > Please let me know if you have any questions / concerns. Looks interesting! I'm not entirely sure what you mean with "submit" though - would

Re: [pytest-dev] Future of pytest-xdist/execnet?

Hey, On Thu, Oct 24, 2019 at 09:45:48AM -0300, Bruno Oliveira wrote: > Because of this, we have been discussing creating a new package, > pytest-xdist2 (other suggestions are welcome), without any backward > compatibility guarantees with pytest-xdist. pytest-[yz]dist? ;) > pytest-xdist2 would, a

[pytest-dev] Upcoming pytest trainings in Switzerland

Hi! I'm happy to announce that I'll give two open pytest trainings in Switzerland: At Europython 2019, 8th July in Basel: https://ep2019.europython.eu/talks/94WEnsY-introduction-to-pytest/ At Workshoptage 2019 (in German), 10th October in Rapperswil: https://workshoptage.ch/workshops/2019/test-d

Re: [pytest-dev] Customising repr() output for super-expressions of failed assertions

Hey, On Thu, Jun 13, 2019 at 12:02:01PM +1200, Craig de Stigter wrote: > This output isn't terribly useful at present. We'd like to automatically > dump the request body (`r.content`) in the output, wherever it's a django > response object, to aid debugging. It'd be cool if this were possible wit

Re: [pytest-dev] Using pytest_assertrepr_compare() for marked tests only?

On Sun, May 12, 2019 at 07:44:01PM -0400, Shawn Brown wrote: > So I have a few related questions I'm hoping someone can help me with: > > Q: Is there a way to reference the current test from within > pytest_assertrepr_compare()? > > Q: If not, is there a decent way to implement something like thi

Re: [pytest-dev] Keeping failing test ids for git bisect

Hey, On Thu, May 02, 2019 at 11:22:08AM +0200, Florian Schulze wrote: > Is there a way to run a bunch of tests like with --lf but don't clear > the cache when they pass? This would be mighty helpful for git bisect. > For now I helped myself by copying the test ids, but that requires > editing the

Re: [pytest-dev] [core] Tidelift Funding

Hey, On Wed, May 01, 2019 at 05:25:58PM -0300, Bruno Oliveira wrote: > there were no obligations whatsoever after joining the platform other than > "maintain the project", which they were already doing anyway. There's no > obligation to market the platform in anyway as well (say, being forced to >

Re: [pytest-dev] Adding a marker to items that have a fixture

On Thu, May 02, 2019 at 02:18:42PM +1200, Craig de Stigter wrote: > This sort of works ( the marker is present by the time the test runs), but > command-line filtering options (`-m 'not solr'`) don't filter based on it. > I guess this hook is running after those options have been consulted? > > I

Re: [pytest-dev] Plans for Europython 2019?

Hey Oliver, On Thu, Apr 25, 2019 at 11:09:15AM +0200, Oliver Bestwalter wrote: > On 4/24/19 9:44 PM, Florian Bruhin wrote:> > > Any other pytest-related plans? Oliver, do you plan to host another > > helpdesk like in 2017/2018? > > Yes, I will propose doing a pytest/

Re: [pytest-dev] Plans for Europython 2019?

On Wed, Apr 24, 2019 at 09:44:50PM +0200, Florian Bruhin wrote: > I might be a bit early since the CfP is not open yet, but hey, why not! I should've waited until this morning ;) The CfP is open now: https://www.europython-society.org/post/184430536360/europython-2019-call-for-proposals

[pytest-dev] Plans for Europython 2019?

Heya, I might be a bit early since the CfP is not open yet, but hey, why not! Given that Europython 2019 is about 1.5h by train away from me and I'm finished with my studies/exams by then, I really want to go there again (finally, after not making it in 2017/2018!) \o/ I'm planning to submit ano

Re: [pytest-dev] document outlining added values

On Tue, Dec 04, 2018 at 12:54:50AM +, Craig de Stigter wrote: > > gradually porting all tests > > Mostly-automated conversion is possible, so it doesn't have to be a gradual > process. > > I wrote a script which converts xunit-style assertions into pytest ones: > https://github.com/craigds/de

Re: [pytest-dev] pyi stubs (PEP 561/ PEP-484) for pytest

Hey Ilya, On Wed, Nov 14, 2018 at 01:19:25AM +0300, Ilya Kazakevich wrote: > My name is Ilya, I develop pytest integration in PyCharm IDE. Yay, thanks for that! \o/ > There is a PEP-484 that covers optional type hinting for Python an > PEP-561 that describes how to distribute this information as

Re: [pytest-dev] Improving pytest internal errors and messages

Hey, On Thu, Oct 04, 2018 at 10:19:21AM -0300, Bruno Oliveira wrote: > This new exception type (I've used UsageError on my PR just for proof of > concept) should be part of the public API so plugins can also use it. > > I'm writing to the ML because it would be beneficial to get feedback from a >

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

On Tue, Jul 31, 2018 at 12:53:51PM +0100, Dave Hunt wrote: > I’d like to add a code of conduct for my pytest plugins, and as > they’re mostly under the pytest organisation on GitHub I thought it > would make sense to use the same as the pytest project. I was > surprised to find that the pytest proj

Re: [pytest-dev] Partnership possibility with Pytest

On Tue, Jul 31, 2018 at 09:13:01AM -0700, Alex Georgie wrote: > >Where would the money go? > We actually work with an organization called OpenCollective ( > https://opencollective.com/) that creates a non-profit for you. The idea is > they handle the legalese and create an account where donations c

Re: [pytest-dev] Code of conduct for pytest organisation on GitHub

On Tue, Jul 31, 2018 at 08:12:10PM +0200, Floris Bruynooghe wrote: > I'm agree that we should probably have a code of conduct. We had one > for the sprint (we used https://www.python.org/psf/codeofconduct/ + 2 > contact details for violations) and I'm surprised it stopped at the > sprint. Probabl

Re: [pytest-dev] Partnership possibility with Pytest

Hi, some random thoughts: FWIW I'm -1 on this (mainly because we don't have a good way to recieve and distribute money; and I doubt there is one at all), but currently a bit in a hurry. On Tue, Jul 31, 2018 at 09:46:10AM +0200, RonnyPfannschmidt wrote: > i like the Idea i`m def +1 on adding this

Re: [pytest-dev] command line options not working?

On Sat, Jul 28, 2018 at 03:12:30PM -0700, Derek Sisson wrote: > I've been using command line options for years, but they no longer work for > me. I get the message "unrecognized arguments". Works fine here (with 3.6.4 as well). > As a sanity check, I used the example from the documentation on > h

Re: [pytest-dev] [PROPOSAL] switchgin over from gitmate via pytestbot to gitmate as an github app

On Fri, Jul 06, 2018 at 10:05:46PM +0200, RonnyPfannschmidt wrote: > not that i'm aware of, > but given the regular mislabeling i'm considering disabling it > altogether instead I did disable linking of related issues and automatic applying of labels a while ago for qutebrowser, because indeed it'

Re: [pytest-dev] Disable pushing directly to features and master branches

On Fri, Jul 06, 2018 at 12:13:12PM -0300, Bruno Oliveira wrote: > Hi everyone, > > GitHub has started issue warnings that the email service we use to notify > pushes to master and features will be discontinued (and we suspect it is > not working correctly either). > > Given that we now invite peo

[pytest-dev] Unsubscribing from pytest-dev/pytest notifications

Hi, (I accidentally sent this to pytest-...@pytest.org rather than @python.org originally. It didn't bounce, but I have no idea where it went :D) this is a difficult step to take, but during three sleepless nights because of health issues last week (don't worry, it's getting better now) I realize

Re: [pytest-dev] Stickers

Hey Bruno, On Sun, Mar 04, 2018 at 12:41:10PM +, Bruno Oliveira wrote: > Does anyone still have the image we used to make the stickers we got last > sprint? I'm planning to make some more to distribute in the next Python > event in my city. :) Some stuff is here: https://github.com/pytest-dev

Re: [pytest-dev] run id

On Fri, Feb 02, 2018 at 09:51:20PM +, Morgan, Hunter via pytest-dev wrote: > looking for a pytest run id for parameterizing fixture creation to > avoid namespace collisions. I don't follow. Can you please elaborate on what you want exactly and why? Florian -- https://www.qutebrowser.org |

Re: [pytest-dev] [proposal] experiment with adapting gitmate.io for automating issue maintenance/triaging tasks

Hey, GitMate seemed quite useful so far! However, the "the contributor most likely able to help you" messages seemed quite a lot of noise to me. Also, they only pinged people who are subscribed to the repository anyways, and are already doing a lot of work either way. I took the freedom to turn t

Re: [pytest-dev] Proposal: Move adamchainz/pytest-randomly to pytest-dev/pytest-randomly

Hey, (Yay, someone else with a me@ address!) On Sat, Dec 16, 2017 at 05:56:18AM +, Adam Johnson wrote: > As Bruno suggested to me*, I'd like to propose moving pytest-randomly into > the pytest-dev organization. I'd still be the main maintainer :) Sounds good, +1! Florian -- https://www.qu

Re: [pytest-dev] [proposal] experiment with adapting gitmate.io for automating issue maintenance/triaging tasks

On Mon, Dec 11, 2017 at 01:31:05PM +0100, Ronny Pfannschmidt wrote: > Hi, > > when i noticed that bit i was a bit shocked as well, > for pytest i mitigated the issue by switching the commenting user to > pytestbot > > its really a shocking misfeature to me that by default a *real person* > is use

Re: [pytest-dev] [proposal] experiment with adapting gitmate.io for automating issue maintenance/triaging tasks

On Mon, Dec 11, 2017 at 10:10:54AM +0100, RonnyPfannschmidt wrote: > Hi Everyone, > > i enabled gitmate for pytest-dev/pytest, > > currently its set up in the default settings - and as far as i can tell > there are quite some nice opt-in's id like to experiment with in future. Just enabled it fo

Re: [pytest-dev] Proposal: Move davehunt/pytest-metadata to pytest-dev/metadata

On Fri, Dec 01, 2017 at 10:06:51AM -0300, Ana Ribeiro wrote: > I don't know if my +1 means anything since I am not an active maintainer of > pytest, but I definitely give a +1 I'll +1 your +1 then ;-) Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8

[pytest-dev] Doing pre-releases (was: Re: Help testing 3.2.0 release (part 2))

On Mon, Jul 31, 2017 at 11:59:32AM +, Bruno Oliveira wrote: > > (btw - I feel like everyone's life would be easier if we'd just push > > release canditates to PyPI which are installable with --pre. Then we can > > also simply do an rc2 in cases like this) > > > > Hmmm that does sound like a go

Re: [pytest-dev] Help testing 3.2.0 release (part 2)

Hey Bruno, On Mon, Jul 31, 2017 at 11:31:12AM +, Bruno Oliveira wrote: > I have prepared another package for the 3.2.0 release and again it would be > great if people could help test it. Thanks! Seems to work fine with qutebrowser this time :) > The package is available at: > > https://

Re: [pytest-dev] How to deal with setup.py/setup.cfg ?

Hi, On Wed, Jul 19, 2017 at 04:02:34PM +0200, Bastien Sevajol wrote: > All tests are collected. setup.cfg (addopts part) is the fail. I need this > "addopts" part because when some developpers who work on the project create > a virtualenv inside the project, pytest search into the venv folder (i a

Re: [pytest-dev] Sponsored pytest stickers

On Mon, Jun 19, 2017 at 08:35:54AM +0200, holger krekel wrote: > Hi Floris, > > On Fri, Jun 16, 2017 at 22:05 +0200, Floris Bruynooghe wrote: > > > > Hi, > > > > Raphael Pierzina writes: > > > I am planning to order a batch of pytest stickers for PyData Berlin > > > and EuroPython. The folks ov

Re: [pytest-dev] proposal: experiment with going for setup.cfg metadata for pylib/pytest/pytest-*

Hi, On Mon, Jun 05, 2017 at 11:10:00AM +0200, RonnyPfannschmidt wrote: > for demonstrative purposes i experimented with it in > https://github.com/pytest-dev/apipkg/pull/2 It already seems to break things in various ways on Travis, for starters. > in terms of maintenance i def prefer the modern

Re: [pytest-dev] pytest 3.1 warning capture woes

On Mon, May 29, 2017 at 08:26:42PM +0200, RonnyPfannschmidt wrote: > Hi everyone, > > while taking a closer look and trying to understand what cpython does, i > stumbled upon > https://github.com/python/cpython/blob/v3.6.1/Lib/unittest/main.py#L77 > > so their default runner just crudely pushes a

Re: [pytest-dev] [proposal] abolishing the features branch

On Wed, Apr 19, 2017 at 11:42:29AM +, Bruno Oliveira wrote: > On Mon, Apr 17, 2017 at 3:49 PM Ronny Pfannschmidt < > opensou...@ronnypfannschmidt.de> wrote: > > > > > On 14.04.2017 14:17, Florian Bruhin wrote: > > > On Thu, Apr 13, 2017 at 05:51:34PM +000

Re: [pytest-dev] the potential need to release 4.0 instead of 3.1, proposal

On Wed, May 17, 2017 at 09:27:09PM +, Bruno Oliveira wrote: > Unless somebody has other points for discussion, I believe once we merge > that PR we can go for the 3.1 release, what do you guys think? Go for it! :) I gave it a try with qutebrowser, and other than pytest-warnings breaking[1] (w

Re: [pytest-dev] the potential need to release 4.0 instead of 3.1, proposal

On Tue, May 16, 2017 at 07:13:24PM +, Bruno Oliveira wrote: > Hi everyone, > > On Fri, May 12, 2017 at 7:03 PM Ronny Pfannschmidt < > opensou...@ronnypfannschmidt.de> wrote: > > > with the recent discovery of > > https://github.com/pytest-dev/pytest/issues/2398 which was a result of > > accid

Re: [pytest-dev] Remove AUTHORS file?

On Thu, May 04, 2017 at 02:24:36PM +, Bruno Oliveira wrote: > On Thu, May 4, 2017 at 11:07 AM Floris Bruynooghe wrote: > > > What's nice is that AUTHORS is just an alphabetical list of people while > > the github page ranks people implicitly by some random metric. It's > > also possible for

Re: [pytest-dev] [proposal] abolishing the features branch

On Thu, Apr 13, 2017 at 05:51:34PM +, Bruno Oliveira wrote: > What if we instead of considering features, we released a new minor version > periodically, for say every month or two? We could adopt the same for bug > fix releases, like each two weeks. FWIW what GitLab[1] does is a monthly featu

Re: [pytest-dev] [proposal] abolishing the features branch

Hi, On Thu, Apr 13, 2017 at 06:25:22PM +0200, Ronny Pfannschmidt wrote: > since quite a while now we keep a lot of code away from users by leaving > it in the features branch, > more recent detail https://github.com/pytest-dev/pytest/issues/2365 > where even i didn't realize we had a fix since hal

Re: [pytest-dev] [3.1 feature] "assert not raise exception" helper: opinions about the name

On Wed, Apr 05, 2017 at 06:41:05PM +0200, Dmitry Dygalo wrote: > Hello everyone! > > Here is my 2 ,-. > What do you think about the following syntax? > > with not pytest.raises(): > foo() > > or > > with not pytest.raises(BaseException): > foo() > > Is it possible to negate pytest.rais

Re: [pytest-dev] [3.1 feature] "assert not raise exception" helper: opinions about the name

On Wed, Apr 05, 2017 at 05:49:24PM +0200, Ronny Pfannschmidt wrote: > i meant the except clause I know, I was just pointing out that there's no valid use case for pytest.raises(None) already, as None can never be raised. In fact, pytest.raises(None) already *does* error out, even on Python 2:

Re: [pytest-dev] [3.1 feature] "assert not raise exception" helper: opinions about the name

Hey, On Wed, Apr 05, 2017 at 05:25:01PM +0200, Ronny Pfannschmidt wrote: > while experimenting i learned of the fun fact that None is a "valid > exception type" > for except clauses on at least python 2.7 But it doesn't seem to be possible to raise it: Python 2.7.13 (default, Dec 21 2016, 07

Re: [pytest-dev] [3.1 feature] "assert not raise exception" helper: opinions about the name

Hi, On Thu, Mar 30, 2017 at 04:12:30PM +, Bruno Oliveira wrote: >- pytest.does_not_raise; I like that name - seems like proper English to me, while the others don't. > *Another question* is if someone sees a problem in making it a singleton > like in the example above, or if we should fo

Re: [pytest-dev] Slow startup

Hey, * Joel Nothman [2017-03-08 17:10:48 +1100]: > plugins: mpl-0.7, cov-2.4.0 Can you try if uninstalling those (or perhaps starting with "-p no:mpl no:cov") helps? Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.or

Re: [pytest-dev] possibly upsetting question on annotations

* oliver [2017-03-04 17:18:10 +]: > Is there really no way that this will *ever* be fixed so we don't need to > use strings or forward declaration hack? Did you mean to write this to python-dev instead of pytest-dev? Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP

Re: [pytest-dev] Reviving pytest-commit

* Floris Bruynooghe [2017-02-20 16:01:43 -0300]: > Those of you subscribed to pytest-commit may have noticed I tried to > revive it as it had been dead since the github migration. On an > unrelated issue I noticed I actually used this a fair bit when it was > working. > > Sadly github will only

Re: [pytest-dev] Google Summer of Code

* Bruno Oliveira [2017-01-25 10:27:09 +]: > On Wed, Jan 25, 2017 at 6:47 AM holger krekel wrote: > > > I'll leave the question of if/how to apply as org/suborg to others > > as i am not bound to mentor myself (see my other post). > > > > Which post do you mean Holger? I didn't receive any o

Re: [pytest-dev] pypy rejecting scrambled mails now, action decission needed - proposing pytest-dev@python.org

* opensou...@ronnypfannschmidt.de [2017-01-22 20:36:27 +0100]: > i propose putting pytest-dev@python.org there. Sounds good to me - or just remove the author_mail argument entirely if PyPI is fine with that. Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 91

Re: [pytest-dev] t-shirts and stickers now out, thanks Florian!

* oliver [2016-11-29 11:54:35 +]: > Where can we see it and order? It looks like this: https://twitter.com/flubdevork/status/803320121980751873 They were ordered for the pytest crowdfunding and sprint only. However, we ordered some extra shirts (mainly black, in XL/L/M if I remember correct

Re: [pytest-dev] t-shirts and stickers now out, thanks Florian!

Hey, * Bruno Oliveira [2016-11-28 19:39:51 +]: > Just received mine, the shirt looks really cool! Glad to hear that! Makes me wonder where it was stuck for a month :D Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compil

Re: [pytest-dev] Remove me from this list, my email: eacosta1...@gmail.com

Hi, you can unsubscribe yourself by sending a mail with the subject 'unsubscribe' to pytest-dev-requ...@python.org, or by doing so here: https://mail.python.org/mailman/options/pytest-dev Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | h

Re: [pytest-dev] T-Shirt has arrived!

Hey Tom, * Tom Viner [2016-11-04 10:21:08 +]: > Am I wearing it right btw? I tried the other way first, but the ticket > label thing was at the front. Yep, the print is supposed to be on the back :) Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0

Re: [pytest-dev] T-Shirt has arrived!

Hey Ted, * Ted [2016-11-04 10:33:38 +0800]: > It is exciting the package arrived in Shanghai, Thanks a lot! Glad to hear that! And it didn't even take the 1-6 months which packages in the opposite direction usually take for me ;) Florian -- http://www.the-compiler.org | m...@the-compiler.org

Re: [pytest-dev] t-shirts and stickers now out, thanks Florian!

* Ronny Pfannschmidt [2016-10-25 15:15:06 +0200]: > Given the funding volumes and used amounts, > i wonder if, with the funds that are left, we could have the next > sprints sponsored mostly by cooperates > next time, > > I propose that those of us working in a company that could/should > partic

Re: [pytest-dev] t-shirts and stickers now out, thanks Florian!

Hey, * holger krekel [2016-10-25 13:04:11 +0200]: > Florian and Regina visited last weekend, did most of the work on > sending out shirts and stickers for both pytest and qutebrowser. > Many thanks to Florian who spend almost a week alltogether preparing > the shirts, stickers, figuring out and m

Re: [pytest-dev] Fwd: Re: Proposal: python namespacign for markings/marker objects

* Ronny Pfannschmidt [2016-10-20 09:07:47 +0200]: > > Finally, and I only just remembered, Holger has some lingering code > > somewhere which does something like: > > > > @pytest.marker > > def blocker(n): > > return {'issue no': int(n)} # or whatever object you want your marker > > to be >

Re: [pytest-dev] the sorry state of pylib tests and pylib

* holger krekel [2016-09-27 18:30:35 +0200]: > On Tue, Sep 27, 2016 at 18:07 +0200, Florian Bruhin wrote: > > * Bruno Oliveira [2016-09-27 14:25:43 +]: > > > Yes, but those downstream projects would have the option o pinning to > > > pylib > > > <

Re: [pytest-dev] the sorry state of pylib tests and pylib

* Bruno Oliveira [2016-09-27 14:25:43 +]: > Yes, but those downstream projects would have the option o pinning to pylib > < 2. Plus I think there must be almost no projects using it, it seems very > pytest specific, that was one of the reasonings we used to justify > vendoring py.code into pyt

Re: [pytest-dev] transfer repo / pypi access / ML announce

Hey, * holger krekel [2016-09-14 13:58:18 +0200]: > I am a bit concerned that people who transfer repos to pytest-dev > think that it receives magic maintenance I read your sentence saying this does happen, and not that you're concerned that it could happen, right? If so, what makes you think t

Re: [pytest-dev] [proposal] deprecating the pytest_namespace hook

* Floris Bruynooghe [2016-09-05 12:11:12 +0100]: > > > the second problem it creates is, it makes the pytest namespace > > > impossible to introspect for external tools > > > > > > I agree that's annoying, but that's a problem in general on how dynamic > > > pytest is (IDEs don't autocomp

Re: [pytest-dev] 3.0.1 tonight?

* Bruno Oliveira [2016-08-23 16:12:03 +]: > Since 3.0.0 was released, two regressions have been reported and this > afternoon the fix for the last one was merged. > > Unless someone still has some issue that they would like to work on for > this release, I was thinking of making a 3.0.1 relea

Re: [pytest-dev] [TIP] pytest 3.0.0 pre-release

* Florian Bruhin [2016-08-18 20:40:19 +0200]: > Hey, > > * Bruno Oliveira [2016-08-18 18:11:41 +]: > > The pytest team has generated a 3.0.0 release candidate and would like to > > ask users to test the new package with their test suites. > > Thanks Bruno! >

Re: [pytest-dev] [TIP] pytest 3.0.0 pre-release

Hey, * Bruno Oliveira [2016-08-18 18:11:41 +]: > The pytest team has generated a 3.0.0 release candidate and would like to > ask users to test the new package with their test suites. Thanks Bruno! The good news: It works fine for me! The bad news: Minus the BDD tests of course... so I'll n

Re: [pytest-dev] Remove invocation fixtures from 3.0?

Hey, * Bruno Oliveira [2016-08-15 01:15:14 +]: > I've worked on the weekend on the issue discovered by Florian on the > qutebrowser test suite, and unfortunately I think the current > implementation will have to be re-thought because it contains a serious > problem regarding finalizers when f

[pytest-dev] GitHub and PR base branch switching

Hey, good news, GitHub now allows to switch the base branch for pull requests: https://github.com/blog/2224-change-the-base-branch-of-a-pull-request Some while ago they also added notifications for new PR pushes: https://github.com/blog/2203-email-updates-about-your-own-activity (at the bottom)

Re: [pytest-dev] pytest and Mozilla's Open Source Support program

* Sivan Greenberg [2016-08-08 14:20:32 +0300]: > P.S. Has anybody documented the sprint in a free form documentation or > were they only closed bugs in the issue tracker and new commits made? :) I > would love to read some summary of the sprint achievements and it's story > as I really feel I m

[pytest-dev] pytest and Mozilla's Open Source Support program

Hey, via [1] (German) I just stumbled upon Mozilla's MOSS program[2]. They have a track[3] where they found generic OSS projects furthering their mission, and another one[4] (probably more relevant to us) where they fund projects they use themselves. From what I've seen via Dave Hunt, Mozilla is

Re: [pytest-dev] 3.0 next week?

Hey, * Bruno Oliveira [2016-08-04 22:59:51 +]: > 1) Early in the week, create and publish a pytest-3.0 package on my devpi > channel [1] and ask people to test it on twitter and the relevant mailing > lists; > 2) If there are no blocking issues reported, release it to PyPI on Thursday; > 3) T

Re: [pytest-dev] 3.0 next week?

Hey, my 0.02 $currency on this: * Bruno Oliveira [2016-08-04 22:59:51 +]: > Is everyone OK with releasing pytest 3.0 next week? My idea is to: I'd love that, but let's take a quick look at what we *wanted* in 3.0 first. Anything which is not either a bug introduced since the last release,

Re: [pytest-dev] Dependency CI

* Brianna Laugher [2016-07-16 16:06:49 +1000]: > This is a new service thing that is free for open source projects. > https://dependencyci.com/ > > Is it worth investigating for pytest and plugins? I've tried it and it didn't detect my requirements.txt (requirements-foo.txt in a subfolder), nor

Re: [pytest-dev] Postpone 3.0?

* Floris Bruynooghe [2016-07-15 15:29:18 +0100]: > On 14 July 2016 at 23:45, Brianna Laugher wrote: > > It's mainly Floris, Oliver and me that are the hold up right? Removing > > reinterpret assert and 2x docs. > > Reinterpret is now removed as of this morning! I should do one more > PR with so

Re: [pytest-dev] Blog RSS invalid

* Floris Bruynooghe [2016-07-04 12:56:25 +0100]: > Hi blog creation people, > > I was going to submit blog.pytest.org to planet.python.org, however > one of the checks they do is validation and it seems our blog fails to > validate: > > https://validator.w3.org/feed/check.cgi?url=http://blog.pyt

Re: [pytest-dev] rewrite-plugins & AppVeyor

Hey, * Floris Bruynooghe [2016-07-04 11:03:11 +0100]: > Hello, > > For the rewrite-plugins PR > (https://github.com/pytest-dev/pytest/pull/1641) the AppVeyor build > seems to have timed out but has no obvious failures. Is AppVeyor > always this unreliable? It means mergable PRs are marked as h

Re: [pytest-dev] Request to bundle Pytest-finer-verdicts as a default plugin with pytest

* 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 tran

Re: [pytest-dev] On-the-ground sprint communication

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 > :-) > >

[pytest-dev] Sprint: GPG keysigning

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 c

Re: [pytest-dev] Climbing at the sprint

* 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

Re: [pytest-dev] CFP EuroPython 2016

* 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

Re: [pytest-dev] My gripes with pytest and tox

* 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://bitbuc

  1   2   >