Hey,
Hopefully we're all aware of the Python Steering Council and its
relationship with various people and groups that do work on Python.
There's also now a proposed similar group for Packaging,
https://peps.python.org/pep-0772/
This got me thinking about the governance and decision process around
ment, which
> defaults to True.
>
> []
> Bruno
>
>> On Sun, Mar 21, 2021 at 2:41 PM Brian Okken wrote:
>> I think I want to get some extra help on this good question.
>> - Brian
>>
>> - Brian
>>
>> Begin forwarded message:
>>
I think I want to get some extra help on this good question.
- Brian
- Brian
Begin forwarded message:
> From: Dimitri Blyumin via Fireside
> Date: March 20, 2021 at 7:36:58 PM PDT
> To: br...@pythontesting.net
> Subject: [Test & Code : Python Testing] Listener Feedback from Dimitri
> Blyumin
Bruno,
This is brilliant in that it’s obvious now that I see it, but didn’t occur to
me before.
Super cool.
- Brian
> On Jan 6, 2021, at 10:26 AM, Bruno Oliveira wrote:
>
>
> Hi James,
>
> What I suggest you do in your case is to decouple your code from the fixture,
> so if you have so
Twitter is good for this.
- Brian
> On Nov 18, 2020, at 12:15 AM, 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 commun
Bruno,
Thanks for the great and rapid info.
- Brian
> On Oct 6, 2020, at 10:07 AM, Bruno Oliveira wrote:
>
>
> Hey Brian,
>
>
>> On Tue, Oct 6, 2020 at 1:55 PM Brian Okken wrote:
>> Hi,
>>
>> How do plugins support multiple pytest versions wh
Hi,
How do plugins support multiple pytest versions when the hook api changes?
Or should they?
Example.
pytest-json-report ytest_warning_captured, which was deprecated in pytest
6.
Looks like there's a new hook, pytest_warning_recorded, with similar enough
API.
I haven't tested it to see if the b
I'd even be more than ok with a context manager approach and even using
asserts within the context manager.
As long as you can have more than one assert fail within the context.
-Brian
On Fri, Mar 27, 2020 at 9:30 AM Brian Okken
wrote:
> Victor,
>
> This would be brilliant. The
test, but just not stopping execution.
This is also the reason why many people resort to subtest.
-Brian Okken
On Fri, Mar 27, 2020 at 9:19 AM Victor Maryama
wrote:
> Oh sure, I see now what you mean.
>
> Back then when I was thinking about this subject it seemed to me that soft
>
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. &qu
hmidt.de> wrote:
> >>> >>
> >>> >> Hi all,
> >>> >>
> >>> >> it seems to me that a change to
> >>> >>
> >>> >>
> https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mar
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 ex
Dave, Jim,
Would you want this need mentioned on either Test & Code or Python Bytes
podcast?
I don’t have bandwidth to help out, but perhaps some listeners do. But I don’t
want to mention if you’d rather I didn’t.
- Brian
> On Nov 30, 2018, at 11:15 AM, Dave Hunt wrote:
>
> Due to a change
Hi,
Is there a way to get a fixture scope such that it runs setup before the
first parametrization of a test and teardown after the last parametrization?
Best I've come up with so far is putting each test into a class and using a
class scope fixture. But it seems like a hack.
Thanks,
I have seen something like what you are describing here:
https://pypi.org/project/pytest-regtest/
- Brian Okken
> On Apr 17, 2018, at 2:22 PM, Vasily Kuznetsov wrote:
>
> Hi everyone!
>
> It would be nice to have an approval testing plugin for pytest, but it seems
>
Bruno,
Please, merge that PR!
caveat: I have not reviewed the code.
However, ...
I get numerous questions about it, and I always tell people to create
artificial dependencies between fixtures that need to run in a certain
order.
The general mental model that people have for fixtures is that they
Hello all,
I kinda feel bad that this has turned into kind-of an ordeal.
Or at least it seems like it has.
I'm rather rooting for the "params" version, and agree with Floris that
"parametrize" should be supported for eternity.
This is not something urgent, of course.
One option is to implement t
Matt Craig (@astronomatty)
8/25/17, 2:15 PM
"Fun" fact: pytest fails with an obscure error if a dir name has dashes in it.
pic.twitter.com/3JGzWBcqqO
Not sure if this is a reported issue or even real. But I saw it on twitter and
thought I'd pass it along.
I'd personally like to see an example to show the new API proposal. How would
it look to a user? How would it look to a plugin dev?
- Brian
Sent from my iPhone
> On Aug 25, 2017, at 7:13 AM, RonnyPfannschmidt
> wrote:
>
> Hi everyone,
>
> as far as i am concerned, we cant hope to safe the
My opinion:
- make 3.1.1 with this feature opt in
- new features that change behavior in backwards incompatible way should be opt
in.
- once the warnings system works, make it a recommended practice to turn it on.
- make sure --strict and warnings -> errors works
> On May 25, 2017, at 5:29 PM,
I don't get the "broke the API" part of this issue.
What used to work and doesn't now?
Is this really significant enough to warrant bumping to 4.0.
Are you ready to follow through with the deprecating promise of
https://docs.pytest.org/en/latest/backwards-compatibility.html so soon after
the i
I have recommended Bruno's solution several times.
Same model works with unittest.
If Ronny's idea moves forward I'd rather see that as a plugin than in core if
possible.
- Brian
> On Aug 31, 2016, at 10:48 AM, Bruno Oliveira wrote:
>
> Hi Ronny,
>
> We’ve had the same need at work, althou
ng it doesn't get
to hold up shipment to get fixed.
My two cents.
BTW. Thanks for all the hard work to get 3.0 out, and all the previous work
you've done on the project.
- Brian Okken
> On Aug 14, 2016, at 6:15 PM, Bruno Oliveira wrote:
>
> Hi everyone,
>
> I've
> - should it be a little animal? should it be abstract?
not an animal
> - should it contain the text "pytest" or "py.test" or nothing?
no opinion
> - should it have snakes?
I'm tired of the snake theme. It works for the python logo, but everywhere
else I've seen it, meh.
> - should it have a go
24 matches
Mail list logo
