From buelter.christoph at gmail.com Wed Dec 4 07:37:35 2019 From: buelter.christoph at gmail.com (Christoph Buelter) Date: Wed, 4 Dec 2019 13:37:35 +0100 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching Message-ID: Greetings, the -k EXPRESSION matching behaviour of the pytest CLI, which deselects tests based on the given expression, is case-sensitive. The relevant code of the KeywordMapping is just a few lines: https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L59-L63 That means using pytest -k statistics will match def test_statistics(): ... but it will not match: class TestStatistics: ... I would have to do some shenanigans like pytest -k "atistics" or pytest -k "statistics or Statistics" to match both tests, just because one happens to be a class and the other a function. Personally, I find that a bit strict and limiting, considering it tests for string inclusion which is rather lax in comparison. It would be very convenient to be able to match both with a single expression, e.g. to filter tests by topics. I know I can mark tests or add extra_keyword_matches, but that isn't very convenient. I also acknowledge that the default behaviour can't be changed as it would break existing code. I have not found a way to customize this with the existing CLI/hooks. Do you think there is any possibility to add some CLI/config option like "--case-insensitive-expression" to make this configurable, or do you consider this to belong to userland? A hook to allow changing the behaviour from a pytest plugin would be totally sufficient as well. I'd be willing to provide a PR if there is any interest. My current workaround is to monkeypatch the behaviour at runtime, which does the job, but is kind of magical and will break when pytests internal structure changes in the future: https://gist.github.com/cb109/de0cf181aaaadf13539be9854c53586c Thanks for pytest by the way :) Cheers, Christoph -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Wed Dec 4 08:58:09 2019 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 4 Dec 2019 10:58:09 -0300 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: Message-ID: Hi Christoph, On Wed, Dec 4, 2019 at 9:38 AM Christoph Buelter < buelter.christoph at gmail.com> wrote: > Greetings, > > the -k EXPRESSION matching behaviour of the pytest CLI, which deselects > tests based on the given expression, is case-sensitive. > More than once I've myself wished that it would be case-insensitive. :) > I also acknowledge that the default behaviour can't be changed as it would > break existing code. > Not sure, -k is usually used interactively, not being part of CI configuration ("usually", I certainly can see it being used as such to select a sub-set of tests for a specific CI run, for example "-k integration"). > I have not found a way to customize this with the existing CLI/hooks. > > Do you think there is any possibility to add some CLI/config option like > "--case-insensitive-expression" to make this configurable, or do you > consider this to belong to userland? A hook to allow changing the behaviour > from a pytest plugin would be totally sufficient as well. I'd be willing to > provide a PR if there is any interest. > 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" than an exact match, as it matches against any portion of the node id currently anyway. Does anybody sees this differently? Cheers, Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Wed Dec 4 09:19:38 2019 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 4 Dec 2019 15:19:38 +0100 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: Message-ID: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> 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" than an exact match, as it matches against any portion of > the node id currently anyway. Sounds entirely reasonable to me! Florian -- me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From variedthoughts at gmail.com Wed Dec 4 09:55:25 2019 From: variedthoughts at gmail.com (Brian Okken) Date: Wed, 4 Dec 2019 06:55:25 -0800 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> Message-ID: <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> I think switching to case insensitive by default would be fine. Do we need a flag for case sensitive? Not sure. - Brian > On Dec 4, 2019, at 6:26 AM, Florian Bruhin wrote: > > ?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" than an exact match, as it matches against any portion of >> the node id currently anyway. > > Sounds entirely reasonable to me! > > Florian > > -- > me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org > https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ > GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > I love long mails! | https://email.is-not-s.ms/ > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From opensource at ronnypfannschmidt.de Wed Dec 4 10:31:16 2019 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Wed, 4 Dec 2019 16:31:16 +0100 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Hi all, it seems to me that a change to https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 in addition to ensuring lowercase of the expression is all that's needed on the technical side on the release management side its a breaking change that needs a major release nonetheless i'm all for it. i wonder about the case sensitivity of mark expressions as well -- Ronny Am 04.12.19 um 15:55 schrieb Brian Okken: > I think switching to case insensitive by default would be fine. Do we need a flag for case sensitive? Not sure. > > - Brian > >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin wrote: >> >> ?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" than an exact match, as it matches against any portion of >>> the node id currently anyway. >> Sounds entirely reasonable to me! >> >> Florian >> >> -- >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org >> https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ >> GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc >> I love long mails! | https://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 From nicoddemus at gmail.com Wed Dec 4 15:56:15 2019 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 4 Dec 2019 17:56:15 -0300 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Thanks everyone for their input! Christoph feel free to open a PR targeting the `features` branch with this change. For now I don't think we need an option to revert to the old behavior; if people claim for it we can consider adding it in the future though. Cheers, Bruno On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt < opensource at ronnypfannschmidt.de> wrote: > Hi all, > > it seems to me that a change to > > > https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 > > > in addition to ensuring lowercase of the expression is all that's needed > on the technical side > > on the release management side its a breaking change that needs a major > release > > nonetheless i'm all for it. > > i wonder about the case sensitivity of mark expressions as well > > > -- Ronny > > > Am 04.12.19 um 15:55 schrieb Brian Okken: > > I think switching to case insensitive by default would be fine. Do we > need a flag for case sensitive? Not sure. > > > > - Brian > > > >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin wrote: > >> > >> ?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" than an exact match, as it matches against any portion > of > >>> the node id currently anyway. > >> Sounds entirely reasonable to me! > >> > >> Florian > >> > >> -- > >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org > >> https://bruhin.software/ | > https://github.com/sponsors/The-Compiler/ > >> GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > >> I love long mails! | https://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 > _______________________________________________ > 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 oscar.j.benjamin at gmail.com Wed Dec 4 17:41:33 2019 From: oscar.j.benjamin at gmail.com (Oscar Benjamin) Date: Wed, 4 Dec 2019 22:41:33 +0000 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: As an aside, I would often like to use -k and have an exact match so e.g. I do $ pytest -k test_xxx and I want that to run test_xxx only and not test_xxx_1 etc. Is there a way to do that? -- Oscar On Wed, 4 Dec 2019 at 20:56, Bruno Oliveira wrote: > > Thanks everyone for their input! > > Christoph feel free to open a PR targeting the `features` branch with this change. > > For now I don't think we need an option to revert to the old behavior; if people claim for it we can consider adding it in the future though. > > Cheers, > Bruno > > On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt wrote: >> >> Hi all, >> >> it seems to me that a change to >> >> https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 >> >> >> in addition to ensuring lowercase of the expression is all that's needed >> on the technical side >> >> on the release management side its a breaking change that needs a major >> release >> >> nonetheless i'm all for it. >> >> i wonder about the case sensitivity of mark expressions as well >> >> >> -- Ronny >> >> >> Am 04.12.19 um 15:55 schrieb Brian Okken: >> > I think switching to case insensitive by default would be fine. Do we need a flag for case sensitive? Not sure. >> > >> > - Brian >> > >> >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin wrote: >> >> >> >> ?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" than an exact match, as it matches against any portion of >> >>> the node id currently anyway. >> >> Sounds entirely reasonable to me! >> >> >> >> Florian >> >> >> >> -- >> >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org >> >> https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ >> >> GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc >> >> I love long mails! | https://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 >> _______________________________________________ >> 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 nicoddemus at gmail.com Wed Dec 4 17:58:24 2019 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 4 Dec 2019 19:58:24 -0300 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Hi Oscar, Not right now, the matching is always partial... not sure how we could signal to `-k` that we want an exact match of the last part of the node id (which seems what you want). Cheers, On Wed, Dec 4, 2019 at 7:40 PM Oscar Benjamin wrote: > As an aside, I would often like to use -k and have an exact match so e.g. > I do > > $ pytest -k test_xxx > > and I want that to run test_xxx only and not test_xxx_1 etc. Is there > a way to do that? > > -- > Oscar > > On Wed, 4 Dec 2019 at 20:56, Bruno Oliveira wrote: > > > > Thanks everyone for their input! > > > > Christoph feel free to open a PR targeting the `features` branch with > this change. > > > > For now I don't think we need an option to revert to the old behavior; > if people claim for it we can consider adding it in the future though. > > > > Cheers, > > Bruno > > > > On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt < > opensource at ronnypfannschmidt.de> wrote: > >> > >> Hi all, > >> > >> it seems to me that a change to > >> > >> > https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 > >> > >> > >> in addition to ensuring lowercase of the expression is all that's needed > >> on the technical side > >> > >> on the release management side its a breaking change that needs a major > >> release > >> > >> nonetheless i'm all for it. > >> > >> i wonder about the case sensitivity of mark expressions as well > >> > >> > >> -- Ronny > >> > >> > >> Am 04.12.19 um 15:55 schrieb Brian Okken: > >> > I think switching to case insensitive by default would be fine. Do we > need a flag for case sensitive? Not sure. > >> > > >> > - Brian > >> > > >> >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin > wrote: > >> >> > >> >> ?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" than an exact match, as it matches against any > portion of > >> >>> the node id currently anyway. > >> >> Sounds entirely reasonable to me! > >> >> > >> >> Florian > >> >> > >> >> -- > >> >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org > >> >> https://bruhin.software/ | > https://github.com/sponsors/The-Compiler/ > >> >> GPG: 916E B0C8 FD55 A072 | > https://the-compiler.org/pubkey.asc > >> >> I love long mails! | https://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 > >> _______________________________________________ > >> 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 flub at devork.be Wed Dec 4 18:12:40 2019 From: flub at devork.be (Floris Bruynooghe) Date: Thu, 5 Dec 2019 00:12:40 +0100 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Using the full test id as shown by -v is what I always use for this case instead of using -k On Wed, 4 Dec 2019, 23:58 Bruno Oliveira, wrote: > Hi Oscar, > > Not right now, the matching is always partial... not sure how we could > signal to `-k` that we want an exact match of the last part of the node id > (which seems what you want). > > Cheers, > > On Wed, Dec 4, 2019 at 7:40 PM Oscar Benjamin > wrote: > >> As an aside, I would often like to use -k and have an exact match so e.g. >> I do >> >> $ pytest -k test_xxx >> >> and I want that to run test_xxx only and not test_xxx_1 etc. Is there >> a way to do that? >> >> -- >> Oscar >> >> On Wed, 4 Dec 2019 at 20:56, Bruno Oliveira wrote: >> > >> > Thanks everyone for their input! >> > >> > Christoph feel free to open a PR targeting the `features` branch with >> this change. >> > >> > For now I don't think we need an option to revert to the old behavior; >> if people claim for it we can consider adding it in the future though. >> > >> > Cheers, >> > Bruno >> > >> > On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt < >> opensource at ronnypfannschmidt.de> wrote: >> >> >> >> Hi all, >> >> >> >> it seems to me that a change to >> >> >> >> >> https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 >> >> >> >> >> >> in addition to ensuring lowercase of the expression is all that's >> needed >> >> on the technical side >> >> >> >> on the release management side its a breaking change that needs a major >> >> release >> >> >> >> nonetheless i'm all for it. >> >> >> >> i wonder about the case sensitivity of mark expressions as well >> >> >> >> >> >> -- Ronny >> >> >> >> >> >> Am 04.12.19 um 15:55 schrieb Brian Okken: >> >> > I think switching to case insensitive by default would be fine. Do >> we need a flag for case sensitive? Not sure. >> >> > >> >> > - Brian >> >> > >> >> >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin >> wrote: >> >> >> >> >> >> ?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" than an exact match, as it matches against any >> portion of >> >> >>> the node id currently anyway. >> >> >> Sounds entirely reasonable to me! >> >> >> >> >> >> Florian >> >> >> >> >> >> -- >> >> >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org >> >> >> https://bruhin.software/ | >> https://github.com/sponsors/The-Compiler/ >> >> >> GPG: 916E B0C8 FD55 A072 | >> https://the-compiler.org/pubkey.asc >> >> >> I love long mails! | https://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 >> >> _______________________________________________ >> >> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From oscar.j.benjamin at gmail.com Wed Dec 4 18:22:06 2019 From: oscar.j.benjamin at gmail.com (Oscar Benjamin) Date: Wed, 4 Dec 2019 23:22:06 +0000 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Ah thanks. I guess you mean $ pytest somefile.py::test_xxx which does indeed work. It would be nice if that string were included in the output from test failures. -- Oscar On Wed, 4 Dec 2019 at 23:12, Floris Bruynooghe wrote: > > Using the full test id as shown by -v is what I always use for this case instead of using -k > > On Wed, 4 Dec 2019, 23:58 Bruno Oliveira, wrote: >> >> Hi Oscar, >> >> Not right now, the matching is always partial... not sure how we could signal to `-k` that we want an exact match of the last part of the node id (which seems what you want). >> >> Cheers, >> >> On Wed, Dec 4, 2019 at 7:40 PM Oscar Benjamin wrote: >>> >>> As an aside, I would often like to use -k and have an exact match so e.g. I do >>> >>> $ pytest -k test_xxx >>> >>> and I want that to run test_xxx only and not test_xxx_1 etc. Is there >>> a way to do that? >>> >>> -- >>> Oscar >>> >>> On Wed, 4 Dec 2019 at 20:56, Bruno Oliveira wrote: >>> > >>> > Thanks everyone for their input! >>> > >>> > Christoph feel free to open a PR targeting the `features` branch with this change. >>> > >>> > For now I don't think we need an option to revert to the old behavior; if people claim for it we can consider adding it in the future though. >>> > >>> > Cheers, >>> > Bruno >>> > >>> > On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt wrote: >>> >> >>> >> Hi all, >>> >> >>> >> it seems to me that a change to >>> >> >>> >> https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 >>> >> >>> >> >>> >> in addition to ensuring lowercase of the expression is all that's needed >>> >> on the technical side >>> >> >>> >> on the release management side its a breaking change that needs a major >>> >> release >>> >> >>> >> nonetheless i'm all for it. >>> >> >>> >> i wonder about the case sensitivity of mark expressions as well >>> >> >>> >> >>> >> -- Ronny >>> >> >>> >> >>> >> Am 04.12.19 um 15:55 schrieb Brian Okken: >>> >> > I think switching to case insensitive by default would be fine. Do we need a flag for case sensitive? Not sure. >>> >> > >>> >> > - Brian >>> >> > >>> >> >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin wrote: >>> >> >> >>> >> >> ?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" than an exact match, as it matches against any portion of >>> >> >>> the node id currently anyway. >>> >> >> Sounds entirely reasonable to me! >>> >> >> >>> >> >> Florian >>> >> >> >>> >> >> -- >>> >> >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org >>> >> >> https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ >>> >> >> GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc >>> >> >> I love long mails! | https://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 >>> >> _______________________________________________ >>> >> 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 From variedthoughts at gmail.com Wed Dec 4 18:37:06 2019 From: variedthoughts at gmail.com (Brian Okken) Date: Wed, 4 Dec 2019 15:37:06 -0800 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Oscar, > " It would be nice if that string were included in the output from test failures. " I'm pretty sure it is. ... =========================== short test summary info =========================== FAILED test_foo.py::test_one_more ===================== 1 failed, 1 passed in 0.16 seconds ====================== ... - Brian On Wed, Dec 4, 2019 at 3:21 PM Oscar Benjamin wrote: > Ah thanks. I guess you mean > > $ pytest somefile.py::test_xxx > > which does indeed work. It would be nice if that string were included > in the output from test failures. > > -- > Oscar > > On Wed, 4 Dec 2019 at 23:12, Floris Bruynooghe wrote: > > > > Using the full test id as shown by -v is what I always use for this case > instead of using -k > > > > On Wed, 4 Dec 2019, 23:58 Bruno Oliveira, wrote: > >> > >> Hi Oscar, > >> > >> Not right now, the matching is always partial... not sure how we could > signal to `-k` that we want an exact match of the last part of the node id > (which seems what you want). > >> > >> Cheers, > >> > >> On Wed, Dec 4, 2019 at 7:40 PM Oscar Benjamin < > oscar.j.benjamin at gmail.com> wrote: > >>> > >>> As an aside, I would often like to use -k and have an exact match so > e.g. I do > >>> > >>> $ pytest -k test_xxx > >>> > >>> and I want that to run test_xxx only and not test_xxx_1 etc. Is there > >>> a way to do that? > >>> > >>> -- > >>> Oscar > >>> > >>> On Wed, 4 Dec 2019 at 20:56, Bruno Oliveira > wrote: > >>> > > >>> > Thanks everyone for their input! > >>> > > >>> > Christoph feel free to open a PR targeting the `features` branch > with this change. > >>> > > >>> > For now I don't think we need an option to revert to the old > behavior; if people claim for it we can consider adding it in the future > though. > >>> > > >>> > Cheers, > >>> > Bruno > >>> > > >>> > On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt < > opensource at ronnypfannschmidt.de> wrote: > >>> >> > >>> >> Hi all, > >>> >> > >>> >> it seems to me that a change to > >>> >> > >>> >> > https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 > >>> >> > >>> >> > >>> >> in addition to ensuring lowercase of the expression is all that's > needed > >>> >> on the technical side > >>> >> > >>> >> on the release management side its a breaking change that needs a > major > >>> >> release > >>> >> > >>> >> nonetheless i'm all for it. > >>> >> > >>> >> i wonder about the case sensitivity of mark expressions as well > >>> >> > >>> >> > >>> >> -- Ronny > >>> >> > >>> >> > >>> >> Am 04.12.19 um 15:55 schrieb Brian Okken: > >>> >> > I think switching to case insensitive by default would be fine. > Do we need a flag for case sensitive? Not sure. > >>> >> > > >>> >> > - Brian > >>> >> > > >>> >> >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin > wrote: > >>> >> >> > >>> >> >> ?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" than an exact match, as it matches against any > portion of > >>> >> >>> the node id currently anyway. > >>> >> >> Sounds entirely reasonable to me! > >>> >> >> > >>> >> >> Florian > >>> >> >> > >>> >> >> -- > >>> >> >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org > >>> >> >> https://bruhin.software/ | > https://github.com/sponsors/The-Compiler/ > >>> >> >> GPG: 916E B0C8 FD55 A072 | > https://the-compiler.org/pubkey.asc > >>> >> >> I love long mails! | https://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 > >>> >> _______________________________________________ > >>> >> 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 > _______________________________________________ > 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 variedthoughts at gmail.com Wed Dec 4 18:40:10 2019 From: variedthoughts at gmail.com (Brian Okken) Date: Wed, 4 Dec 2019 15:40:10 -0800 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Oops. My bad. I'm used to running with -ra or -rf, which will produce the summary with the test names. - Brian On Wed, Dec 4, 2019 at 3:37 PM Brian Okken wrote: > Oscar, > > " It would be nice if that string were included in the output from test > failures. " > I'm pretty sure it is. > ... > =========================== short test summary info > =========================== > FAILED test_foo.py::test_one_more > ===================== 1 failed, 1 passed in 0.16 seconds > ====================== > ... > - Brian > > > > On Wed, Dec 4, 2019 at 3:21 PM Oscar Benjamin > wrote: > >> Ah thanks. I guess you mean >> >> $ pytest somefile.py::test_xxx >> >> which does indeed work. It would be nice if that string were included >> in the output from test failures. >> >> -- >> Oscar >> >> On Wed, 4 Dec 2019 at 23:12, Floris Bruynooghe wrote: >> > >> > Using the full test id as shown by -v is what I always use for this >> case instead of using -k >> > >> > On Wed, 4 Dec 2019, 23:58 Bruno Oliveira, wrote: >> >> >> >> Hi Oscar, >> >> >> >> Not right now, the matching is always partial... not sure how we could >> signal to `-k` that we want an exact match of the last part of the node id >> (which seems what you want). >> >> >> >> Cheers, >> >> >> >> On Wed, Dec 4, 2019 at 7:40 PM Oscar Benjamin < >> oscar.j.benjamin at gmail.com> wrote: >> >>> >> >>> As an aside, I would often like to use -k and have an exact match so >> e.g. I do >> >>> >> >>> $ pytest -k test_xxx >> >>> >> >>> and I want that to run test_xxx only and not test_xxx_1 etc. Is there >> >>> a way to do that? >> >>> >> >>> -- >> >>> Oscar >> >>> >> >>> On Wed, 4 Dec 2019 at 20:56, Bruno Oliveira >> wrote: >> >>> > >> >>> > Thanks everyone for their input! >> >>> > >> >>> > Christoph feel free to open a PR targeting the `features` branch >> with this change. >> >>> > >> >>> > For now I don't think we need an option to revert to the old >> behavior; if people claim for it we can consider adding it in the future >> though. >> >>> > >> >>> > Cheers, >> >>> > Bruno >> >>> > >> >>> > On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt < >> opensource at ronnypfannschmidt.de> wrote: >> >>> >> >> >>> >> Hi all, >> >>> >> >> >>> >> it seems to me that a change to >> >>> >> >> >>> >> >> https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 >> >>> >> >> >>> >> >> >>> >> in addition to ensuring lowercase of the expression is all that's >> needed >> >>> >> on the technical side >> >>> >> >> >>> >> on the release management side its a breaking change that needs a >> major >> >>> >> release >> >>> >> >> >>> >> nonetheless i'm all for it. >> >>> >> >> >>> >> i wonder about the case sensitivity of mark expressions as well >> >>> >> >> >>> >> >> >>> >> -- Ronny >> >>> >> >> >>> >> >> >>> >> Am 04.12.19 um 15:55 schrieb Brian Okken: >> >>> >> > I think switching to case insensitive by default would be fine. >> Do we need a flag for case sensitive? Not sure. >> >>> >> > >> >>> >> > - Brian >> >>> >> > >> >>> >> >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin >> wrote: >> >>> >> >> >> >>> >> >> ?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" than an exact match, as it matches against any >> portion of >> >>> >> >>> the node id currently anyway. >> >>> >> >> Sounds entirely reasonable to me! >> >>> >> >> >> >>> >> >> Florian >> >>> >> >> >> >>> >> >> -- >> >>> >> >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org >> >>> >> >> https://bruhin.software/ | >> https://github.com/sponsors/The-Compiler/ >> >>> >> >> GPG: 916E B0C8 FD55 A072 | >> https://the-compiler.org/pubkey.asc >> >>> >> >> I love long mails! | https://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 >> >>> >> _______________________________________________ >> >>> >> 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 >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Thu Dec 5 00:00:33 2019 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Thu, 5 Dec 2019 06:00:33 +0100 Subject: [pytest-dev] [proposal] installing the psf-chronegrapher into pytest-dev Message-ID: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> Hi everyone, in https://github.com/pytest-dev/pytest/issues/6080 it was noted that https://github.com/apps/psf-chronographer ensures towncrier notes are in prs, i would like to? propose enabling it for all of pytest-dev ?Ronny From jimbrannlund at fastmail.com Thu Dec 5 03:02:51 2019 From: jimbrannlund at fastmail.com (=?UTF-8?Q?Jim_Br=C3=A4nnlund?=) Date: Thu, 05 Dec 2019 09:02:51 +0100 Subject: [pytest-dev] =?utf-8?q?=5Bproposal=5D_installing_the_psf-chroneg?= =?utf-8?q?rapher_into_pytest-dev?= In-Reply-To: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> References: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> Message-ID: What would that entail for maintainers of projects under the pytest-dev umbrella? //Jim -- Jim Br?nnlund jimbrannlund at fastmail.com On Thu, Dec 5, 2019, at 6:00 AM, RonnyPfannschmidt wrote: > Hi everyone, > > > in https://github.com/pytest-dev/pytest/issues/6080 it was noted that > https://github.com/apps/psf-chronographer ensures towncrier notes are in > prs, > i would like to? propose enabling it for all of pytest-dev > > > ?Ronny > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From ned at nedbatchelder.com Thu Dec 5 05:27:24 2019 From: ned at nedbatchelder.com (Ned Batchelder) Date: Thu, 5 Dec 2019 05:27:24 -0500 Subject: [pytest-dev] [proposal] installing the psf-chronegrapher into pytest-dev In-Reply-To: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> References: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> Message-ID: <54e880a0-9528-802a-c706-2b6ffabb8b8b@nedbatchelder.com> On 12/5/19 12:00 AM, RonnyPfannschmidt wrote: > Hi everyone, > > > in https://github.com/pytest-dev/pytest/issues/6080 it was noted that > https://github.com/apps/psf-chronographer ensures towncrier notes are > in prs, > i would like to? propose enabling it for all of pytest-dev > > Like Jim, I would like to have more details about what this would mean for each repo in the pytest-dev org. Does every repo have to adopt towncrier? Additionally, I've never heard of the "pyba" org that authored this bot, and that org has no public members, so I can't even see who is writing this bot.? Can we encourage them to be more transparent? --Ned. From buelter.christoph at gmail.com Thu Dec 5 08:37:08 2019 From: buelter.christoph at gmail.com (Christoph Buelter) Date: Thu, 5 Dec 2019 14:37:08 +0100 Subject: [pytest-dev] -k EXPRESSION: How to allow for case-insensitive matching In-Reply-To: References: <20191204141938.gsiuonsb6ch3uvaj@hooch.localdomain> <332CEEC4-FE54-4079-923E-E9781899C3C4@gmail.com> Message-ID: Thanks everyone for your feedback! I have created a PR: https://github.com/pytest-dev/pytest/pull/6316 Let us continue the discussion there, please let me know what I can do to get this in. Cheers, Christoph Am Do., 5. Dez. 2019 um 00:40 Uhr schrieb Brian Okken < variedthoughts at gmail.com>: > Oops. My bad. > I'm used to running with -ra or -rf, which will produce the summary with > the test names. > - Brian > > On Wed, Dec 4, 2019 at 3:37 PM Brian Okken > wrote: > >> Oscar, >> > " It would be nice if that string were included in the output from test >> failures. " >> I'm pretty sure it is. >> ... >> =========================== short test summary info >> =========================== >> FAILED test_foo.py::test_one_more >> ===================== 1 failed, 1 passed in 0.16 seconds >> ====================== >> ... >> - Brian >> >> >> >> On Wed, Dec 4, 2019 at 3:21 PM Oscar Benjamin >> wrote: >> >>> Ah thanks. I guess you mean >>> >>> $ pytest somefile.py::test_xxx >>> >>> which does indeed work. It would be nice if that string were included >>> in the output from test failures. >>> >>> -- >>> Oscar >>> >>> On Wed, 4 Dec 2019 at 23:12, Floris Bruynooghe wrote: >>> > >>> > Using the full test id as shown by -v is what I always use for this >>> case instead of using -k >>> > >>> > On Wed, 4 Dec 2019, 23:58 Bruno Oliveira, >>> wrote: >>> >> >>> >> Hi Oscar, >>> >> >>> >> Not right now, the matching is always partial... not sure how we >>> could signal to `-k` that we want an exact match of the last part of the >>> node id (which seems what you want). >>> >> >>> >> Cheers, >>> >> >>> >> On Wed, Dec 4, 2019 at 7:40 PM Oscar Benjamin < >>> oscar.j.benjamin at gmail.com> wrote: >>> >>> >>> >>> As an aside, I would often like to use -k and have an exact match so >>> e.g. I do >>> >>> >>> >>> $ pytest -k test_xxx >>> >>> >>> >>> and I want that to run test_xxx only and not test_xxx_1 etc. Is there >>> >>> a way to do that? >>> >>> >>> >>> -- >>> >>> Oscar >>> >>> >>> >>> On Wed, 4 Dec 2019 at 20:56, Bruno Oliveira >>> wrote: >>> >>> > >>> >>> > Thanks everyone for their input! >>> >>> > >>> >>> > Christoph feel free to open a PR targeting the `features` branch >>> with this change. >>> >>> > >>> >>> > For now I don't think we need an option to revert to the old >>> behavior; if people claim for it we can consider adding it in the future >>> though. >>> >>> > >>> >>> > Cheers, >>> >>> > Bruno >>> >>> > >>> >>> > On Wed, Dec 4, 2019 at 12:38 PM RonnyPfannschmidt < >>> opensource at ronnypfannschmidt.de> wrote: >>> >>> >> >>> >>> >> Hi all, >>> >>> >> >>> >>> >> it seems to me that a change to >>> >>> >> >>> >>> >> >>> https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py#L28 >>> >>> >> >>> >>> >> >>> >>> >> in addition to ensuring lowercase of the expression is all that's >>> needed >>> >>> >> on the technical side >>> >>> >> >>> >>> >> on the release management side its a breaking change that needs a >>> major >>> >>> >> release >>> >>> >> >>> >>> >> nonetheless i'm all for it. >>> >>> >> >>> >>> >> i wonder about the case sensitivity of mark expressions as well >>> >>> >> >>> >>> >> >>> >>> >> -- Ronny >>> >>> >> >>> >>> >> >>> >>> >> Am 04.12.19 um 15:55 schrieb Brian Okken: >>> >>> >> > I think switching to case insensitive by default would be fine. >>> Do we need a flag for case sensitive? Not sure. >>> >>> >> > >>> >>> >> > - Brian >>> >>> >> > >>> >>> >> >> On Dec 4, 2019, at 6:26 AM, Florian Bruhin < >>> me at the-compiler.org> wrote: >>> >>> >> >> >>> >>> >> >> ?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" than an exact match, as it matches against >>> any portion of >>> >>> >> >>> the node id currently anyway. >>> >>> >> >> Sounds entirely reasonable to me! >>> >>> >> >> >>> >>> >> >> Florian >>> >>> >> >> >>> >>> >> >> -- >>> >>> >> >> me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org >>> >>> >> >> https://bruhin.software/ | >>> https://github.com/sponsors/The-Compiler/ >>> >>> >> >> GPG: 916E B0C8 FD55 A072 | >>> https://the-compiler.org/pubkey.asc >>> >>> >> >> I love long mails! | https://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 >>> >>> >> _______________________________________________ >>> >>> >> 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 >>> _______________________________________________ >>> 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 Thu Dec 5 20:46:55 2019 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 5 Dec 2019 22:46:55 -0300 Subject: [pytest-dev] pytest 4.6.7 released Message-ID: pytest 4.6.7 has just been released to PyPI. This is a bug-fix release for the 4.6.X series, the last pytest series that supports Python 2.7 and 3.4, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Bruno Oliveira * Daniel Hahler Happy testing, The pytest Development Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Sat Dec 7 06:28:06 2019 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Sat, 7 Dec 2019 12:28:06 +0100 Subject: [pytest-dev] [proposal] installing the psf-chronegrapher into pytest-dev In-Reply-To: <54e880a0-9528-802a-c706-2b6ffabb8b8b@nedbatchelder.com> References: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> <54e880a0-9528-802a-c706-2b6ffabb8b8b@nedbatchelder.com> Message-ID: Am 05.12.19 um 11:27 schrieb Ned Batchelder: > On 12/5/19 12:00 AM, RonnyPfannschmidt wrote: >> Hi everyone, >> >> >> in https://github.com/pytest-dev/pytest/issues/6080 it was noted that >> https://github.com/apps/psf-chronographer ensures towncrier notes are >> in prs, >> i would like to? propose enabling it for all of pytest-dev >> >> > Like Jim, I would like to have more details about what this would mean > for each repo in the pytest-dev org. Does every repo have to adopt > towncrier? > > Additionally, I've never heard of the "pyba" org that authored this > bot, and that org has no public members, so I can't even see who is > writing this bot.? Can we encourage them to be more transparent? > indeed, its currently not transparent enough, it came out of pip/cypthon and us used for their towncrier style management. before putting it in i will validate what repos will be affected, and more general properties as well as ensuting more transparent documentation of the system. i would like this to support and enable painless voluntary towncrier adoption, but if it turns out not to be able to provide that, we cant use it globally. -- Ronny > --Ned. > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From opensource at ronnypfannschmidt.de Sat Dec 7 06:29:02 2019 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Sat, 7 Dec 2019 12:29:02 +0100 Subject: [pytest-dev] [proposal] installing the psf-chronegrapher into pytest-dev In-Reply-To: References: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> Message-ID: <019ecf0f-9145-9cd5-b5a1-f2b3dd54a25f@ronnypfannschmidt.de> The idea i have in mind is nothing changes for projects not using towncrier, informative extra checks for projects using towncrier. -- Ronny Am 05.12.19 um 09:02 schrieb Jim Br?nnlund: > What would that entail for maintainers of projects under the pytest-dev umbrella? > > //Jim > From ned at nedbatchelder.com Sat Dec 7 09:12:26 2019 From: ned at nedbatchelder.com (Ned Batchelder) Date: Sat, 7 Dec 2019 09:12:26 -0500 Subject: [pytest-dev] [proposal] installing the psf-chronegrapher into pytest-dev In-Reply-To: References: <9ce00e8e-05f0-75da-13bc-3cf101c55dbd@ronnypfannschmidt.de> <54e880a0-9528-802a-c706-2b6ffabb8b8b@nedbatchelder.com> Message-ID: <31304089-8855-5592-98c5-c4b57918948d@nedbatchelder.com> On 12/7/19 6:28 AM, RonnyPfannschmidt wrote: > > Am 05.12.19 um 11:27 schrieb Ned Batchelder: >> On 12/5/19 12:00 AM, RonnyPfannschmidt wrote: >>> Hi everyone, >>> >>> >>> in https://github.com/pytest-dev/pytest/issues/6080 it was noted >>> that https://github.com/apps/psf-chronographer ensures towncrier >>> notes are in prs, >>> i would like to? propose enabling it for all of pytest-dev >>> >>> >> Like Jim, I would like to have more details about what this would >> mean for each repo in the pytest-dev org. Does every repo have to >> adopt towncrier? >> >> Additionally, I've never heard of the "pyba" org that authored this >> bot, and that org has no public members, so I can't even see who is >> writing this bot.? Can we encourage them to be more transparent? >> > indeed, its currently not transparent enough, > it came out of pip/cypthon and us used for their towncrier style > management. > > before putting it in i will validate what repos will be affected, > and more general properties as well as ensuting more transparent > documentation of the system. > > i would like this to support and enable painless voluntary towncrier > adoption, > but if it turns out not to be able to provide that, we cant use it > globally. That sounds great to me.? We're considering towncrier for Open edX, so I'm interested to learn more about how it works in practice. > > -- Ronny > >> --Ned. >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev From opensource at ronnypfannschmidt.de Sun Dec 8 15:30:20 2019 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Sun, 8 Dec 2019 21:30:20 +0100 Subject: [pytest-dev] returning from my break and choosing my role Message-ID: <8d0b6e3c-23e7-6fb4-2ccf-c0b088a33353@ronnypfannschmidt.de> Hi everyone, in the last few weeks i have ramped up my involvement with pytest after taking a longer break. In my time of reflection i came to a few conclusions i want to share. The need for my break after all in part originated from caring too much about things that don't actually matter to me as a person. Its not sensible for me to stay on top of all the things and it destroys the time frames i actually have for contributing the things that i want to bring in. Back around 2005 when i i started with pytest, it was very simple and i could actually easily fix issues with pytest in a testsuite for that little while it took Holger to actually pick it up and fix it better in pytest itself. Over the following years, as my involvement with pytest grew and expanded, the feature-set pf pytest, as well as our technical debt from trying hard not to break things for users grew. Between 2016 i had taken it very hardly on myself that we cannot nicely iterate on this technical debt which turned pytest from something where i can easily fix a bug that affects my testsuite from my testsuite into something where that is not the case anymore. I had also taken it in on myself that some issues (like marker transfer between sibling classes) would affect some users gravely. And a fix was incredible hard to come by back then. My self-introspection while taking the pause has lead me to a few questions and my personal answers. What do i want to be responsible for ? What do i want to feel responsible for ? What do i want out of my Involvement ? Its important to answer those with a good base-level of the "good selfishness" which is there to preserve our own selves in the world and to assert our own position. In future i will no longer be on top of all the issues in some sense (in fact, ignoring issues that don't spark my interest has left me with time to do more about things that i care about, both pytest and other things). In future i will work on guiding and developing pytest into a direction where users will actually be able to fix bugs that affect them in a own testsuite until we fix it right. In future i will work on community building - i want the community of pytest to grow, i want the number of pytest core developers to grow and i want the number of active umbrella plugins to grow. For that a vibrant, including and encouraging community setup is needed (plus community builder is a great self development goal, i have so many rough edges at community communication that i want to smooth/reshape). And while aiming for that a primary goal of mine will be joy * joy of developing and bringing things forward * joy of interacting and helping people/myself to grow * joy of being in control of what i do for who and when i do it. I'm choosing a future that i will enjoy and and i invite everyone to join me in the journey of choosing a personal future abundant with the positive. Whats coming next is that i'm going to keep slowly organizing myself around the changes i want to bring forward and slowly bringing them into reality in small sustainable steps. Part of that already manifests in my proposals/changes to the development processes and the Node Structures. The rest will reveal itself as i refine my own processes and start to communicate better/more structured. Regards, Ronny From nicoddemus at gmail.com Sat Dec 14 08:40:57 2019 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Sat, 14 Dec 2019 10:40:57 -0300 Subject: [pytest-dev] pytest 5.3.2 Message-ID: pytest 5.3.2 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Anthony Sottile * Bruno Oliveira * Claudio Madotto * Daniel Hahler * Jared Vasquez * Michael Rose * Ran Benita * Ronny Pfannschmidt * Zac Hatfield-Dodds Happy testing, The pytest Development Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From asottile+pytest at umich.edu Thu Dec 19 19:05:06 2019 From: asottile+pytest at umich.edu (Anthony Sottile) Date: Thu, 19 Dec 2019 16:05:06 -0800 Subject: [pytest-dev] pytest 4.6.8 released! Message-ID: pytest 4.6.8 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Anthony Sottile * Bruno Oliveira * Ryan Mast Happy testing, The pytest Development Team From nicoddemus at gmail.com Mon Dec 23 05:25:05 2019 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 23 Dec 2019 07:25:05 -0300 Subject: [pytest-dev] returning from my break and choosing my role In-Reply-To: <8d0b6e3c-23e7-6fb4-2ccf-c0b088a33353@ronnypfannschmidt.de> References: <8d0b6e3c-23e7-6fb4-2ccf-c0b088a33353@ronnypfannschmidt.de> Message-ID: Thanks a lot for this e-mail Ronny! It is very important to be comfortable and in a role you enjoy and care about when participating in a open source project like pytest. As we have discussed many times in chat/email, backward compatibility brakages are sometimes necessary and are part of the development and evolution of a long running project, so those are welcome! Myself and the rest of the team sure are glad to have you back! :) Cheers, Bruno. On Sun, Dec 8, 2019 at 5:30 PM RonnyPfannschmidt < opensource at ronnypfannschmidt.de> wrote: > Hi everyone, > > in the last few weeks i have ramped up my involvement with pytest after > taking a longer break. > > In my time of reflection i came to a few conclusions i want to share. > > The need for my break after all in part originated from caring too much > about things that don't actually matter to me as a person. > Its not sensible for me to stay on top of all the things and it destroys > the time frames i actually have for contributing the things that i want > to bring in. > > Back around 2005 when i i started with pytest, it was very simple and i > could actually easily fix issues with pytest in a testsuite > for that little while it took Holger to actually pick it up and fix it > better in pytest itself. > > Over the following years, as my involvement with pytest grew and > expanded, the feature-set pf pytest, > as well as our technical debt from trying hard not to break things for > users grew. > > Between 2016 i had taken it very hardly on myself that we cannot nicely > iterate on this technical debt which turned pytest from something > where i can easily fix a bug that affects my testsuite from my testsuite > into something where that is not the case anymore. > > I had also taken it in on myself that some issues (like marker transfer > between sibling classes) would affect some users gravely. > And a fix was incredible hard to come by back then. > > My self-introspection while taking the pause has lead me to a few > questions and my personal answers. > > What do i want to be responsible for ? > What do i want to feel responsible for ? > What do i want out of my Involvement ? > > Its important to answer those with a good base-level of the "good > selfishness" which is there to preserve our own selves in the world and > to assert our own position. > > In future i will no longer be on top of all the issues in some sense (in > fact, ignoring issues that don't spark my interest has left me with time > to do more about things that i care about, both pytest and other things). > In future i will work on guiding and developing pytest into a direction > where users will actually be able to fix bugs that affect them in a own > testsuite until we fix it right. > In future i will work on community building - i want the community of > pytest to grow, i want the number of pytest core developers to grow and > i want the number of active umbrella plugins to grow. > For that a vibrant, including and encouraging community setup is needed > (plus community builder is a great self development goal, i have so many > rough edges at community communication that i want to smooth/reshape). > > And while aiming for that a primary goal of mine will be joy > * joy of developing and bringing things forward > * joy of interacting and helping people/myself to grow > * joy of being in control of what i do for who and when i do it. > > I'm choosing a future that i will enjoy and and i invite everyone to > join me in the journey of choosing a personal future abundant with the > positive. > > Whats coming next is that i'm going to keep slowly organizing myself > around the changes i want to bring forward and slowly bringing them into > reality in small sustainable steps. > > Part of that already manifests in my proposals/changes to the > development processes and the Node Structures. > > The rest will reveal itself as i refine my own processes and start to > communicate better/more structured. > > Regards, Ronny > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ut at pyngo.tom.ru Tue Dec 24 09:23:57 2019 From: ut at pyngo.tom.ru (Ivan) Date: Tue, 24 Dec 2019 21:23:57 +0700 Subject: [pytest-dev] New plugin: pytest-unordered Message-ID: <6842b3928758d440cabe59f6c4c6b5ff56ab9466.camel@pyngo.tom.ru> Greetings! After participation in this discussion on GitHub https://github.com/pytest-dev/pytest/issues/5548 I have created a new plugin: https://github.com/utapyngo/pytest-unordered I need some feedback on it as it is my first pytest plugin. We have been using in in a commercial project for a month. I also think that it is better to move it to pytest-dev to share some of the maintenance responsibility if such a small plugin is worth it. Ivan