[pytest-dev] pytest-8.2.0

[Bruno Oliveira]

pytest-8.2.0
===

The pytest team is proud to announce the 8.2.0 release!

This release contains new features, improvements, and bug fixes,
the full list of changes is available in the changelog:

https://docs.pytest.org/en/stable/changelog.html

For complete documentation, please visit:

https://docs.pytest.org/en/stable/

As usual, you can upgrade from PyPI via:

pip install -U pytest

Thanks to all of the contributors to this release:

* Bruno Oliveira
* Daniel Miller
* Florian Bruhin
* HolyMagician03-UMich
* John Litborn
* Levon Saldamli
* Linghao Zhang
* Manuel López-Ibáñez
* Pierre Sassoulas
* Ran Benita
* Ronny Pfannschmidt
* Sebastian Meyer
* Shekhar verma
* Tamir Duberstein
* Tobias Stoeckmann
* dj
* jakkdl
* poulami-sau
* tserg


Happy testing,
The pytest Development Team___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest-libfaketime plugin submission to pytest-dev

[Bruno Oliveira]

On Mon, Apr 8, 2024, at 2:41 PM, Floris Bruynooghe wrote:
> On Sat 06 Apr 2024 at 23:43 +0300, Ran Benita via pytest-dev wrote:
> 
> > On Thu, Apr 4, 2024, at 17:47, Éloi Rivard via pytest-dev wrote:
> >> Hi,
> >> I am (also) the maintainer of pytest-libfaketime [1]. It brings and hides 
> >> some boilerplate for using python-libfaketime [2] with pytest.
> >> python-libfaketime has the same purpose than freezegun [3] but does it by 
> >> mocking calls on the C level instead of pythonically, thus it can achieve 
> >> good performances.
> >> 
> >> The project has no heavy activity, but there is actually no need since it 
> >> does not bring a lot of code.
> >> 
> >> I would like to transfer pytest-libfaketime on the pytest-dev github group.
> >> 
> >> The repository is currently on gitlab, but I will move it to github to 
> >> initialize the transfer if this gets the two votes needed.
> >> 
> >> What do you think?
> >> 
> >> Éloi
> >
> > +1 from me.
> 
> +1 as well

+1 from me as well.

In the past I usually was in charge of handling the transfer, but I think it 
would be interesting if some other core contributor could handle the transfer 
this time.
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest-iam plugin submission to pytest-dev

[Bruno Oliveira]

On Sat, Apr 6, 2024, at 5:40 PM, Ran Benita via pytest-dev wrote:
> On Thu, Apr 4, 2024, at 17:32, Éloi Rivard via pytest-dev wrote:
> > Hi,
> 
> Hi
> 
> > I am the maintainer of pytest-iam [1] and its underlying library Canaille 
> > [2].
> > This is a plugin that spawns a lightweight customizable OpenID Connect 
> > server
> > for test purpose. It can be used to check several behaviors of an 
> > application
> > against an OIDC server without mocking the requests.
> > Both projects are actively maintained and Canaille received a NLNet grant 
> > last
> > year.
> >
> > I would like to transfer pytest-iam on the pytest-dev github group.
> >
> > The repository is currently on gitlab, but I will move it to github to
> > initialize the transfer if this gets the two votes needed.
> >
> > What do you think?
> 
> According to the requirements [0] everything checks out (initially I though 
> missing
> a tox.ini file, but I see it's in the pyproject.toml, didn't know this was 
> possible...).
> So +1 from me.

+1 from me as well.

In the past I usually was in charge of handling the transfer, but I think it 
would be interesting if some other core contributor could handle the transfer 
this time.

___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest-7.3.1

[Bruno Oliveira]

pytest 7.3.1 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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Ran Benita


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 7.2.2

[Bruno Oliveira]

pytest 7.2.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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Bruno Oliveira
* Garvit Shubham
* Mahesh Vashishtha
* Ramsey
* Ronny Pfannschmidt
* Teejay
* q0w
* vin01


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Looking for recommendation

[Bruno Oliveira]

Hi Steve,

One technique which I have used for this scenario is to declare a base
class containing the "common" tests. The class should not have the "Test"
prefix/suffix as to not be collected by pytest.

Then on the sibling projects, you create a Test subclass from the base
class, which in turns makes it collectible by pytest. One point you want to
address is how to customize the tests somehow on the sibling project. If
you are already using a fixture based system, it is easy to overwrite the
fixture in the subclass to return project-specific data which makes sense
in that context.

I describe this technique in detail in my pytest book, pytest Quickstart
Guide if you want more details.

Hope this points you in the right direction.

Cheers,
Bruno.

On Mon, Feb 6, 2023 at 1:21 PM Steve  wrote:

> Hello,
>
> I'm look for some advice regarding restructuring tests/test layout for an
> existing project using pytest.
>
> Forgive me if this isn't the correct forum for this sort of questions. I'm
> sending this here because I felt this doesn't
> really qualify as a bug/issue to be raise on github.
>
> Here's what I am looking for -- I'd like to update / restructure test
> within an existing project which initially was
> developed as a webapp for a single client/customer but is now being
> refactored to allow for a multi-client / multi-
> tenent setup.
>
> The current tests layout is pretty standard with the tests/ directory
> living next to the src/ directory and a top-level
> conftest.py with fixtures.
>
> In the new version of the app, we would like to have tests that are:
>
> a. Common for all deployments and are entirely independent of customer
> configuration
> b. Common tests per customer configuration (potentially using
> parameterised fixtures and/or tests)
> c. Customer specific tests (potentially using markers)
>
> I am curious whether there are any best-practices I could adopt and
> pitfalls I ought to be aware of.
>
> Additionally, any recommendations on tests directory layout and fixture
> approaches would also help.
>
> Ideally, the setup should be flexible enough so that we might to exercise
> all the tests (for all customers) or select
> all the common tests + parameterized tests + customer specific tests for a
> specific customer.
>
> I'm considering a combination of using custom commandline options[1] and
> markers to do this.
>
> Does a structure like...
>
> tests
>   |- conftest.py
>   |- tests_common/
>   ||- tests_parameterized.py
>   !|- tests_independent.py
>   |- customer1/
>   ||- conftest.py
>   ||- tests_speciic.py
>   |- customer2/
>   |- ...
>
> make sense ?
>
> I know this is all a bit high-level and vague but I'm trying to learn from
> any of you who might have done this before.
> So, I recognise and appreciate in advance any time you put into replying
> to this.
>
> cheers,
> Steve
>
>
> [1]
> https://docs.pytest.org/en/7.2.x/example/simple.html#control-skipping-of-tests-according-to-command-line-option
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Yes that's why the message came to be hehehe.

It will eventually be mandatory, from my understanding.

Cheers

On Sun, Jan 22, 2023 at 6:47 AM Floris Bruynooghe  wrote:

> So why does tidelift keep telling us every week this isn't completed?
>
> On Fri 20 Jan 2023 at 10:47 -0300, Bruno Oliveira wrote:
>
> > Sorry for the noise folks, pytest is a critical project and 2FA will be
> > mandatory anyway:
> >
> > 2FA requirement
> >
> > Requiring 2FA for this project will require all collaborators to have 2FA
> > enabled for their individual account. Any collaborator who does not have
> > 2FA enabled will not be able to manage the project until they enable 2FA.
> > This project will be part of PyPI's two-factor authentication mandate for
> > critical projects. As a result, this setting cannot be disabled for this
> > project.
> >
> > So no action is required.
> >
> > Cheers,
> > Bruno.
> >
> > On Fri, Jan 20, 2023 at 10:44 AM Bruno Oliveira 
> > wrote:
> >
> >> Hi folks,
> >>
> >> In
> https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html
> >> we agreed on enabling 2FA for pytest-dev on GitHub, which we did.
> >>
> >> How about we do the same for the pytest project in PyPI?
> >>
> >> Cheers,
> >> Bruno.
> >>
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Sorry for the noise folks, pytest is a critical project and 2FA will be
mandatory anyway:

2FA requirement

Requiring 2FA for this project will require all collaborators to have 2FA
enabled for their individual account. Any collaborator who does not have
2FA enabled will not be able to manage the project until they enable 2FA.
This project will be part of PyPI's two-factor authentication mandate for
critical projects. As a result, this setting cannot be disabled for this
project.

So no action is required.

Cheers,
Bruno.

On Fri, Jan 20, 2023 at 10:44 AM Bruno Oliveira 
wrote:

> Hi folks,
>
> In https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html
> we agreed on enabling 2FA for pytest-dev on GitHub, which we did.
>
> How about we do the same for the pytest project in PyPI?
>
> Cheers,
> Bruno.
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Hi folks,

In https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html
we agreed on enabling 2FA for pytest-dev on GitHub, which we did.

How about we do the same for the pytest project in PyPI?

Cheers,
Bruno.
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 7.2.1

[Bruno Oliveira]

pytest 7.2.1 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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Anthony Sottile
* Bruno Oliveira
* Daniel Valenzuela
* Kadino
* Prerak Patel
* Ronny Pfannschmidt
* Santiago Castro
* s-padmanaban


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Submitting pytest-inline plugin

[Bruno Oliveira]

All done:

[image: image.png]

Let me know if anything else is missing.

Also, please add me as a maintainer in PyPI: nicoddemus.

Cheers,
Bruno.

On Sat, Dec 31, 2022 at 1:50 AM Yu Liu (Yuki)  wrote:

> Hi Bruno,
>
> I have transferred the repo pytest-inline to you.
>
> Thanks,
> Yuki
>
> On Fri, Dec 30, 2022 at 9:52 AM Yu Liu (Yuki)  wrote:
>
>> Hi Bruno, Oliver, Floris,
>>
>> Thank you for the feedback! We have updated the README in our repo. We
>> will also update the API from Here to itest, which may take some more
>> time.
>>
>> If nobody objects by tomorrow, Yuki, could you please transfer the
>>> repository to me, as well as send me the GitHub names that should
>>> become admin of the repository once it is part of pytest-dev? Thanks.
>>
>>
>> Sounds good! I will transfer the repo to you later today. We would like
>> to add the following admins: sweetStreet, pengyunie, gliga, and
>> owolabileg.
>>
>> Thanks,
>> Yuki
>>
>> On Thu, Dec 29, 2022 at 3:46 PM Bruno Oliveira 
>> wrote:
>>
>>>
>>>
>>> On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe 
>>> wrote:
>>>
>>>> I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
>>>> perspective.  IIRC we're not vetting the plugins, merely allowing them
>>>> to be taken over if the bus factor becomes fatally low.
>>>>
>>>
>>> That was my understanding as well, the feedback is definitely
>>> nice, however so far we never blocked any transfer due to requests/feedback
>>> like that (not even sure that Oliver meant it in that manner anyway).
>>>
>>> Not that I'm saying the feedback isn't useful either though, maybe file
>>>> it as an issue on the repo? (wait, do they get transferred by github as
>>>> well?)
>>>>
>>>
>>> Yes, everything is transferred accordingly.
>>>
>>> If nobody objects by tomorrow, Yuki, could you please transfer the
>>> repository to me, as well as send me the GitHub names that should become
>>> admin of the repository once it is part of pytest-dev? Thanks.
>>>
>>> Cheers,
>>> Bruno.
>>>
>>>
>>>> Cheers,
>>>> Floris
>>>>
>>>>
>>>> On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:
>>>>
>>>> > I had a look. Interesting idea for sure. A few things though :
>>>> >
>>>> > - the github page should clarify that these tests are intended to go
>>>> in the
>>>> > actual source code, rather than in the test code. Also, whether the
>>>> inline
>>>> > tests are merely empty functions when not hit via pytest.
>>>> > - the github page should mention some important aspect like the
>>>> performance
>>>> > hit as discussed in the article that the page links to, and further
>>>> clarify
>>>> > how this is achieved (because for me, performance was one of my 2
>>>> primany
>>>> > concerns). I'm a little skeptical that it is that low because function
>>>> > calls in Python are relatively expensive but I'm happy to be
>>>> proven
>>>> > wrong. Eg should one be aware that the hit of the article is per test
>>>> > line so putting an inline test in a small loop could result in a
>>>> > measurable hit, etc?
>>>> > - the top-level api, ie `Here()`, needs to be renamed to clarify to
>>>> > would-be readers of the source code that this is inline test code
>>>> that is
>>>> > not run when not reached via pytest. Eg I recommend `itest`, short,
>>>> easy to
>>>> > write, explicit.
>>>> >
>>>> > Cheers,
>>>> > Oliver
>>>> >
>>>> > On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <
>>>> nicodde...@gmail.com>
>>>> > wrote:
>>>> >
>>>> >> Hi Yuki,
>>>> >>
>>>> >> Sorry for the late reply, I think this notification slipped through
>>>> the
>>>> >> cracks.
>>>> >>
>>>> >> We need two +1 votes from members before we can continue with the
>>>> transfer.
>>>> >>
>>>> >> I'm +1, the plugin definitely looks interesting, we need just one
>>>> more
>>>> >> vote then.
>>>> >>
>>&

Re: [pytest-dev] Submitting pytest-inline plugin

[Bruno Oliveira]

On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe  wrote:

> I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
> perspective.  IIRC we're not vetting the plugins, merely allowing them
> to be taken over if the bus factor becomes fatally low.
>

That was my understanding as well, the feedback is definitely nice, however
so far we never blocked any transfer due to requests/feedback like that
(not even sure that Oliver meant it in that manner anyway).

Not that I'm saying the feedback isn't useful either though, maybe file
> it as an issue on the repo? (wait, do they get transferred by github as
> well?)
>

Yes, everything is transferred accordingly.

If nobody objects by tomorrow, Yuki, could you please transfer the
repository to me, as well as send me the GitHub names that should become
admin of the repository once it is part of pytest-dev? Thanks.

Cheers,
Bruno.


> Cheers,
> Floris
>
>
> On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:
>
> > I had a look. Interesting idea for sure. A few things though :
> >
> > - the github page should clarify that these tests are intended to go in
> the
> > actual source code, rather than in the test code. Also, whether the
> inline
> > tests are merely empty functions when not hit via pytest.
> > - the github page should mention some important aspect like the
> performance
> > hit as discussed in the article that the page links to, and further
> clarify
> > how this is achieved (because for me, performance was one of my 2 primany
> > concerns). I'm a little skeptical that it is that low because function
> > calls in Python are relatively expensive but I'm happy to be proven
> > wrong. Eg should one be aware that the hit of the article is per test
> > line so putting an inline test in a small loop could result in a
> > measurable hit, etc?
> > - the top-level api, ie `Here()`, needs to be renamed to clarify to
> > would-be readers of the source code that this is inline test code that is
> > not run when not reached via pytest. Eg I recommend `itest`, short, easy
> to
> > write, explicit.
> >
> > Cheers,
> > Oliver
> >
> > On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, 
> > wrote:
> >
> >> Hi Yuki,
> >>
> >> Sorry for the late reply, I think this notification slipped through the
> >> cracks.
> >>
> >> We need two +1 votes from members before we can continue with the
> transfer.
> >>
> >> I'm +1, the plugin definitely looks interesting, we need just one more
> >> vote then.
> >>
> >> Cheers,
> >> Bruno.
> >>
> >> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) 
> wrote:
> >>
> >>> Dear pytest developers,
> >>>
> >>> We would like to submit our plugin “pytest-inline” to pytest-dev
> >>> organization. pytest-inline is a plugin to help developers write
> >>> inline tests at statement level. Inline testing is a new granularity
> >>> of testing that make it easier to check individual program statements.
> >>> An inline test is a statement that allows to provide arbitrary inputs
> >>> and test oracles for checking the immediately preceding statement that
> >>> is not an inline test. We have a paper about inline tests:
> >>> https://arxiv.org/abs/2209.06315.
> >>>
> >>> Our current repo is at
> >>> https://github.com/EngineeringSoftware/pytest-inline. We have followed
> >>> the guidelines to prepare the repo. We have also uploaded the plugin
> >>> to PyPI. All of our contributors agreed to transfer the repo. Please
> >>> let us know if you need any further information. Look forward to your
> >>> feedback.
> >>>
> >>> Thanks,
> >>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
> >>> ___
> >>> pytest-dev mailing list
> >>> pytest-dev@python.org
> >>> https://mail.python.org/mailman/listinfo/pytest-dev
> >>>
> >> ___
> >> pytest-dev mailing list
> >> pytest-dev@python.org
> >> https://mail.python.org/mailman/listinfo/pytest-dev
> >>
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Submitting pytest-inline plugin

[Bruno Oliveira]

Hi Yuki,

Sorry for the late reply, I think this notification slipped through the
cracks.

We need two +1 votes from members before we can continue with the transfer.

I'm +1, the plugin definitely looks interesting, we need just one more vote
then.

Cheers,
Bruno.

On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki)  wrote:

> Dear pytest developers,
>
> We would like to submit our plugin “pytest-inline” to pytest-dev
> organization. pytest-inline is a plugin to help developers write
> inline tests at statement level. Inline testing is a new granularity
> of testing that make it easier to check individual program statements.
> An inline test is a statement that allows to provide arbitrary inputs
> and test oracles for checking the immediately preceding statement that
> is not an inline test. We have a paper about inline tests:
> https://arxiv.org/abs/2209.06315.
>
> Our current repo is at
> https://github.com/EngineeringSoftware/pytest-inline. We have followed
> the guidelines to prepare the repo. We have also uploaded the plugin
> to PyPI. All of our contributors agreed to transfer the repo. Please
> let us know if you need any further information. Look forward to your
> feedback.
>
> Thanks,
> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Enabled!

This removed 41 users from the organization, including Holger!

GitHub will contact those users mentioning the reason, hopefully people
will enable 2FA and ask us to rejoin.

Cheers,
Bruno.

On Thu, Dec 8, 2022 at 3:10 PM oliver  wrote:

> Makes sense to me.
>
> On Thu, Dec 8, 2022 at 11:42 AM Floris Bruynooghe  wrote:
>
>> I'd also be +1 on this.
>>
>> Note however that the user in question did have 2FA enabled already and
>> indeed this doesn't help for compromised tokens.  I think we can force
>> some limits on what tokens are allowed, I'm not entirely sure here and
>> on how restricting this may turn out to be for people.
>>
>> Anyway, requiring 2FA is a decent step I support.
>>
>> Cheers,
>> Floris
>>
>>
>> On Thu 08 Dec 2022 at 13:17 -0300, Bruno Oliveira wrote:
>>
>> > Hi folks,
>> >
>> > Given the recent incident of suspicious activity using a stolen
>> credential
>> > from a pytest-dev org member, it was suggested that pytest is
>> high-enough
>> > profile that we should require 2FA for all members.
>> >
>> > I'm definitely +1 on this, sending this message here in case someone
>> wants
>> > to voice concerns.
>> >
>> > Cheers,
>> > Bruno.
>> > ___
>> > pytest-dev mailing list
>> > pytest-dev@python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Hi folks,

I intend to enable the requirement in a few hours, unless someone objects.

Cheers,
Bruno.

On Thu, Dec 8, 2022 at 1:17 PM Bruno Oliveira  wrote:

> Hi folks,
>
> Given the recent incident of suspicious activity using a stolen credential
> from a pytest-dev org member, it was suggested that pytest is high-enough
> profile that we should require 2FA for all members.
>
> I'm definitely +1 on this, sending this message here in case someone wants
> to voice concerns.
>
> Cheers,
> Bruno.
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Enabling 2FA for pytest-dev

[Bruno Oliveira]

Hi folks,

Given the recent incident of suspicious activity using a stolen credential
from a pytest-dev org member, it was suggested that pytest is high-enough
profile that we should require 2FA for all members.

I'm definitely +1 on this, sending this message here in case someone wants
to voice concerns.

Cheers,
Bruno.
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] github compromised account on organisation

[Bruno Oliveira]

Thanks Floris.

Yes, please go ahead and contact the user.

I've posted a thread about this for the Core team in the pytest-dev
Discussions, just for reference:

https://github.com/orgs/pytest-dev/teams/core/discussions/23

Cheers,
Bruno.

On Thu, Dec 8, 2022 at 10:18 AM Floris Bruynooghe  wrote:

> Hi folks,
>
> Github recently sent an email warning of a member of the pytest-dev org
> (I'm purposefully not adding identifiable information here) likely
> having a compromised API token that may have been abused.  The member in
> question only has read access to all but one plugin repository so the
> impact is limited.
>
> Nevertheless we should probably contact them to ask for them to make
> sure they revoke all API tokens, replace them with more limited-scopes
> ones if possible and audit the plugin.  If they can't do this or don't
> respond I guess we should (temporarily) restrict their access to the
> plugin as well.
>
> I'm happy to contact them, but also didn't do so yet just in case
> multiple folks jump on this.  Probably one is enough.
>
> Cheers,
> Floris
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Candidate plugin "pytest-tcpclient"

[Bruno Oliveira]

All done!

Next step would be for you to open PRs updating URLs in README, docs, etc.

Cheers, and thanks for moving pytest-tcpclient over to pytest-dev!



On Thu, Nov 17, 2022 at 6:10 PM Anders Lindstrom 
wrote:

> On it's way.
>
> On Fri, 18 Nov 2022 at 08:04, Bruno Oliveira  wrote:
>
>> 2 is enough. You can transfer the repository to me.
>>
>>
>>
>> On Thu, Nov 17, 2022 at 5:46 PM Anders Lindstrom <
>> and...@anderslindstrom.com> wrote:
>>
>>> Okay. Thanks.
>>>
>>> What’s the next step? How many votes are required before I can transfer
>>> to pytest administrator?
>>>
>>> Anders.
>>>
>>> On Fri, 18 Nov 2022 at 07:24, Floris Bruynooghe  wrote:
>>>
>>>> Hello,
>>>>
>>>> +1 from me too.
>>>>
>>>> Cheers,
>>>> Floris
>>>>
>>>>
>>>> On Wed 16 Nov 2022 at 08:18 -0300, Bruno Oliveira wrote:
>>>>
>>>> > Hello Anders,
>>>> >
>>>> > I did take a look at the plugin and it does fit all requirements.
>>>> >
>>>> > +1 from me.
>>>> >
>>>> > Cheers,
>>>> > Bruno
>>>> >
>>>> > On Tue, Nov 15, 2022 at 9:52 PM Anders Lindstrom <
>>>> and...@anderslindstrom.com>
>>>> > wrote:
>>>> >
>>>> >> Hi,
>>>> >>
>>>> >> I've written a pytest plugin called `pytest-tcpclient`. Here it is:
>>>> >>
>>>> >>- https://pypi.org/project/pytest-tcpclient/
>>>> >>
>>>> >> I've checked the prerequisites listed here
>>>> >> <
>>>> https://docs.pytest.org/en/7.1.x/contributing.html#submitting-plugins-to-pytest-dev
>>>> >.
>>>> >> I'm pretty sure it complies.
>>>> >>
>>>> >> I'd like to propose that it be accepted into the `pytest-dev`
>>>> organisation.
>>>> >>
>>>> >> Anders.
>>>> >> ___
>>>> >> pytest-dev mailing list
>>>> >> pytest-dev@python.org
>>>> >> https://mail.python.org/mailman/listinfo/pytest-dev
>>>> >>
>>>> > ___
>>>> > pytest-dev mailing list
>>>> > pytest-dev@python.org
>>>> > https://mail.python.org/mailman/listinfo/pytest-dev
>>>>
>>>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Candidate plugin "pytest-tcpclient"

[Bruno Oliveira]

2 is enough. You can transfer the repository to me.



On Thu, Nov 17, 2022 at 5:46 PM Anders Lindstrom 
wrote:

> Okay. Thanks.
>
> What’s the next step? How many votes are required before I can transfer to
> pytest administrator?
>
> Anders.
>
> On Fri, 18 Nov 2022 at 07:24, Floris Bruynooghe  wrote:
>
>> Hello,
>>
>> +1 from me too.
>>
>> Cheers,
>> Floris
>>
>>
>> On Wed 16 Nov 2022 at 08:18 -0300, Bruno Oliveira wrote:
>>
>> > Hello Anders,
>> >
>> > I did take a look at the plugin and it does fit all requirements.
>> >
>> > +1 from me.
>> >
>> > Cheers,
>> > Bruno
>> >
>> > On Tue, Nov 15, 2022 at 9:52 PM Anders Lindstrom <
>> and...@anderslindstrom.com>
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> I've written a pytest plugin called `pytest-tcpclient`. Here it is:
>> >>
>> >>- https://pypi.org/project/pytest-tcpclient/
>> >>
>> >> I've checked the prerequisites listed here
>> >> <
>> https://docs.pytest.org/en/7.1.x/contributing.html#submitting-plugins-to-pytest-dev
>> >.
>> >> I'm pretty sure it complies.
>> >>
>> >> I'd like to propose that it be accepted into the `pytest-dev`
>> organisation.
>> >>
>> >> Anders.
>> >> ___
>> >> pytest-dev mailing list
>> >> pytest-dev@python.org
>> >> https://mail.python.org/mailman/listinfo/pytest-dev
>> >>
>> > ___
>> > pytest-dev mailing list
>> > pytest-dev@python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Candidate plugin "pytest-tcpclient"

[Bruno Oliveira]

Anders,

Feel free to transfer the repository to me (nicoddemus), and I can move the
transfer forward.

Cheers,
Bruno

On Thu, Nov 17, 2022 at 5:24 PM Floris Bruynooghe  wrote:

> Hello,
>
> +1 from me too.
>
> Cheers,
> Floris
>
>
> On Wed 16 Nov 2022 at 08:18 -0300, Bruno Oliveira wrote:
>
> > Hello Anders,
> >
> > I did take a look at the plugin and it does fit all requirements.
> >
> > +1 from me.
> >
> > Cheers,
> > Bruno
> >
> > On Tue, Nov 15, 2022 at 9:52 PM Anders Lindstrom <
> and...@anderslindstrom.com>
> > wrote:
> >
> >> Hi,
> >>
> >> I've written a pytest plugin called `pytest-tcpclient`. Here it is:
> >>
> >>- https://pypi.org/project/pytest-tcpclient/
> >>
> >> I've checked the prerequisites listed here
> >> <
> https://docs.pytest.org/en/7.1.x/contributing.html#submitting-plugins-to-pytest-dev
> >.
> >> I'm pretty sure it complies.
> >>
> >> I'd like to propose that it be accepted into the `pytest-dev`
> organisation.
> >>
> >> Anders.
> >> ___
> >> pytest-dev mailing list
> >> pytest-dev@python.org
> >> https://mail.python.org/mailman/listinfo/pytest-dev
> >>
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Candidate plugin "pytest-tcpclient"

[Bruno Oliveira]

Hello Anders,

I did take a look at the plugin and it does fit all requirements.

+1 from me.

Cheers,
Bruno

On Tue, Nov 15, 2022 at 9:52 PM Anders Lindstrom 
wrote:

> Hi,
>
> I've written a pytest plugin called `pytest-tcpclient`. Here it is:
>
>- https://pypi.org/project/pytest-tcpclient/
>
> I've checked the prerequisites listed here
> .
> I'm pretty sure it complies.
>
> I'd like to propose that it be accepted into the `pytest-dev` organisation.
>
> Anders.
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] preparing a pytest-dev/core social video meetup and preparing ideas for a online/offline sprint in 2023

[Bruno Oliveira]

Ronny,

Sounds like a good idea, specially having another Sprint in person.

Cheers,
Bruno

On Sat, Oct 8, 2022 at 4:48 AM Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:

> Hi everyone,
>
>
> with the pandemic ensuring lack of safe conferences/sprints since a
> while now,
> i think its very helpful to create some type of semi-regular interaction
> to get the team closer and to foster progress.
>
>
> The last pytest sprint is already an awful long while ago, and with the
> lack of safe to visit conferences in the last few years, we haven't had
> many chances to foster social interaction.
>
> In order to change that i want to create a regular round-table whose
> primary focus is getting to know each other and fostering joy in
> interaction, which in turn should be a good help in fostering progress
> for pytest as a whole.
>
>
> Additionally i would like to see trough with some preparations for a
> pytest summer sprint in 2023
> in order to create opportunities to work in person on some of the pain
> points that we where not able to touch/move in the years since the last
> sprint.
>
>
> -- Ronny
>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Transfer of pyfakefs to pytest-dev - second try

[Bruno Oliveira]

Since nobody objects, I think we can make the transfer.

Feel free to transfer to me Andreas.

Cheers

On Sun, Oct 2, 2022 at 4:24 AM hansemrbean 
wrote:

> Thank you Sorin and Bruno!
>
> The documentation (
> https://docs.pytest.org/en/7.1.x/contributing.html#submitting-plugins-to-pytest-dev)
> states that the repository can be transferred "if no contributor strongly
> objects and two agree". We got two votes, so I will wait a bit more for
> objections, and in the case none come will go ahead with the transfer. How
> long shall we wait, and who shall the repo be transferred to if nobody
> objects?
>
> Thanks,
>
> Andreas
>
>
> Am 01.10.2022 um 20:15 schrieb Bruno Oliveira:
>
> +1 for me too btw.
>
> Cheers,
>
> On Sat, Oct 1, 2022 at 5:08 AM Sorin Sbarnea 
> wrote:
>
>> +1 from me. I think we should show that pytest-dev is an open minded
>> organisation. I remeber when I lead the move of testinfra into it, where we
>> faced a similar dilemma, the fact that it was a little bit more than a
>> pytest plugin. Still, it did work, well I say.
>>
>> To be honest, I reached a point where I do my best to avoid starting to
>> use any new library, if that is not hosted under a non personal account —
>> just because it is not cool to depend on a single point of failure, one
>> that ages too.
>>
>> Cheers!
>> Sorin Sbarnea
>>
>> On Sat, 1 Oct 2022 at 08:04, hansemrbean via pytest-dev <
>> pytest-dev@python.org> wrote:
>>
>>> This is a followup to an earlier thread (
>>> https://www.mail-archive.com/pytest-dev@python.org/msg02835.html) a
>>> year and a half ago, where I asked if it would be possible to transfer
>>> pyfakefs (https://github.com/jmcgeheeiv/pyfakefs) to pytest-dev. This
>>> was eventually declined, mostly because pyfakefs is not a pure pytest
>>> plugin, but also supports unittest and other test environments.
>>>
>>> The maintainer of pyfakefs, John McGehee, has contacted me, and asked me
>>> to take over, as he will not be able to maintain the package anymore. While
>>> discussing this, we again came to the conclusion that moving the repository
>>> to pytest-dev would make much sense. I asked Bruno Oliviera (who helped
>>> with with the transfer of pytest-order) in a private discussion, and he
>>> encouraged me to try again, so here I am...
>>>
>>> I want to reiterate the reasons for the transfer I gave last time, and
>>> maybe elaborate a bit more.
>>>
>>> - ensure continued maintenance: I will be the only maintainer now, and
>>> the move to an organization would make it possible to add other owners, and
>>> will probably make it more likely to find another maintainer (given the
>>> visibility and size of pytest-dev). There is also the bus factor, which I
>>> cannot discard given that I'm not young.
>>>
>>> - increase compatibility with pytest and pytest plugins,
>>>
>>> - improve visibility of the package, especially for pytest developers:
>>>
>>> pyfakefs was originally developed inside Google with the possibility to
>>> mock some filesystem modules and later released on GitHub; John McGehee
>>> added specific support for unittest in 2014, and another contributor added
>>> pytest support in the form of the fs fixture a bit later (2015). Since then
>>> the usage of pyfakefs has steadily drifted from unittest to pytest, as can
>>> be seen by the usage in other repositories (I did some usage statistics for
>>> dependent repos in GitHub) and by new issues, and the support for pytest
>>> has been improved. I personally like pytest and see it as the superior
>>> testing framework, so I'm also interested in improving the compatiblity of
>>> pyfakefs with other pytest plugins - which will be easier if it is clearly
>>> visible as part of the pytest environment.
>>>
>>> - ideally, benefit from the larger community to get more code reviews
>>> and issue reports: if think this is obvious.
>>>
>>> Last time it had also been proposed to move to https://github.com/PyCQA
>>> instead, but I really don't see a match here.
>>> https://github.com/cogs-of-testing had also been mentioned, and while
>>> it sounds like a good match, it has yet to be brought to life.
>>>
>>> Let me know if there is anything I can do to make pyfakefs better
>>> compatible with pytest-dev, or if you need more information.
>>>
>>> Thanks in advance,
>>>
>>> Andreas
>>>
>>>
&g

Re: [pytest-dev] Transfer of pyfakefs to pytest-dev - second try

[Bruno Oliveira]

+1 for me too btw.

Cheers,

On Sat, Oct 1, 2022 at 5:08 AM Sorin Sbarnea 
wrote:

> +1 from me. I think we should show that pytest-dev is an open minded
> organisation. I remeber when I lead the move of testinfra into it, where we
> faced a similar dilemma, the fact that it was a little bit more than a
> pytest plugin. Still, it did work, well I say.
>
> To be honest, I reached a point where I do my best to avoid starting to
> use any new library, if that is not hosted under a non personal account —
> just because it is not cool to depend on a single point of failure, one
> that ages too.
>
> Cheers!
> Sorin Sbarnea
>
> On Sat, 1 Oct 2022 at 08:04, hansemrbean via pytest-dev <
> pytest-dev@python.org> wrote:
>
>> This is a followup to an earlier thread (
>> https://www.mail-archive.com/pytest-dev@python.org/msg02835.html) a year
>> and a half ago, where I asked if it would be possible to transfer pyfakefs (
>> https://github.com/jmcgeheeiv/pyfakefs) to pytest-dev. This was
>> eventually declined, mostly because pyfakefs is not a pure pytest plugin,
>> but also supports unittest and other test environments.
>>
>> The maintainer of pyfakefs, John McGehee, has contacted me, and asked me
>> to take over, as he will not be able to maintain the package anymore. While
>> discussing this, we again came to the conclusion that moving the repository
>> to pytest-dev would make much sense. I asked Bruno Oliviera (who helped
>> with with the transfer of pytest-order) in a private discussion, and he
>> encouraged me to try again, so here I am...
>>
>> I want to reiterate the reasons for the transfer I gave last time, and
>> maybe elaborate a bit more.
>>
>> - ensure continued maintenance: I will be the only maintainer now, and
>> the move to an organization would make it possible to add other owners, and
>> will probably make it more likely to find another maintainer (given the
>> visibility and size of pytest-dev). There is also the bus factor, which I
>> cannot discard given that I'm not young.
>>
>> - increase compatibility with pytest and pytest plugins,
>>
>> - improve visibility of the package, especially for pytest developers:
>>
>> pyfakefs was originally developed inside Google with the possibility to
>> mock some filesystem modules and later released on GitHub; John McGehee
>> added specific support for unittest in 2014, and another contributor added
>> pytest support in the form of the fs fixture a bit later (2015). Since then
>> the usage of pyfakefs has steadily drifted from unittest to pytest, as can
>> be seen by the usage in other repositories (I did some usage statistics for
>> dependent repos in GitHub) and by new issues, and the support for pytest
>> has been improved. I personally like pytest and see it as the superior
>> testing framework, so I'm also interested in improving the compatiblity of
>> pyfakefs with other pytest plugins - which will be easier if it is clearly
>> visible as part of the pytest environment.
>>
>> - ideally, benefit from the larger community to get more code reviews and
>> issue reports: if think this is obvious.
>>
>> Last time it had also been proposed to move to https://github.com/PyCQA
>> instead, but I really don't see a match here.
>> https://github.com/cogs-of-testing had also been mentioned, and while it
>> sounds like a good match, it has yet to be brought to life.
>>
>> Let me know if there is anything I can do to make pyfakefs better
>> compatible with pytest-dev, or if you need more information.
>>
>> Thanks in advance,
>>
>> Andreas
>>
>>
>>
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
> --
> --
> Cheers,
> Sorin
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 7.1.3

[Bruno Oliveira]

pytest 7.1.3 has just been released to PyPI.

This is a bug-fix release, being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The full changelog is available at
https://docs.pytest.org/en/stable/changelog.html.

Thanks to all of the contributors to this release:

* Anthony Sottile
* Bruno Oliveira
* Gergely Kalmár
* Nipunn Koorapati
* Pax
* Sviatoslav Sydorenko
* Tim Hoffmann
* Tony Narlock
* Wolfremium
* Zach OBrien
* aizpurua23a


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest-7.1.2

[Bruno Oliveira]

pytest 7.1.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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Anthony Sottile
* Bruno Oliveira
* Hugo van Kemenade
* Kian Eliasi
* Ran Benita
* Zac Hatfield-Dodds


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest-7.0.1

[Bruno Oliveira]

pytest 7.0.1 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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Anthony Sottile
* Bruno Oliveira
* Ran Benita


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest-parallel submission

[Bruno Oliveira]

Ahh OK thanks Ronny.

So I guess we will have to decline the submission for now Éloi, but thanks
for writing up anyway.

Cheers,
B

On Wed, Sep 15, 2021 at 11:52 AM Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:

> Based on the fact that pytest-parallel massively monkey-patches the
> internals of pytest ,
>
> Im -1 on adding it to pytest-dev
>
> code like
>
> https://github.com/browsertron/pytest-parallel/blob/master/pytest_parallel/__init__.py#L222-L231
> gets me pretty nervous about hopefully upcoming major changes.
>
> until it can be done without monkeypatching pytest internals about
> fixture/session state,
> i would prefer not to have it directly associated with pytest-dev,
>
> I certainly don't want to be responsible for pytest-parallel when we
> break those internals in future.
>
> -- Ronny
>
> Am 02.09.21 um 09:51 schrieb Éloi Rivard:
> >> [...] I think it would be important to have an active maintainer to do
> the
> >> move, otherwise we risk it just staying abandoned, but now in a
> different
> >> place.
> > There are a few volunteers already.
> >
> >> Having said that, I'm +1.
> > Great! Thank you.
> >
> > Éloi
> >
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest-parallel submission

[Bruno Oliveira]

Hi Éloi,

Thanks for bringing this to attention!

However a small caveat, just bringing it to the pytest-dev organization
won't automatically bring maintainers to the project (definitely not from
the core maintainers, as we already are spread thin as is). I think it
would be important to have an active maintainer to do the move, otherwise
we risk it just staying abandoned, but now in a different place.

Having said that, I'm +1.

Having a CHANGELOG is definitely something we want, but can be done after
it has been moved, no problem.

Cheers,
Bruno,

On Wed, Sep 1, 2021 at 12:49 PM Éloi Rivard 
wrote:

> Hi.
> I would like to submit the pytest-parallel [1] project to the github
> pytest-dev group. The current maintainer does not have time to spend on
> the project anymore, and this has been evoked [2] as a solution for the
> community to take over the maintenance.
>
> As required by the documentation:
> - the package is named "pytest-parallel" on pypi [3]
> - it has a tox configuration [4]
> - it has a README [5]
> - it is under MIT LICENSE [6]
> - it has an issue tracker [7]
> - it does not have a changelog yet though, it is blocking?
>
> So now we need two approvals :)
>
> What do you think?
>
>
> [1] https://github.com/browsertron/pytest-parallel/
> [2] https://github.com/browsertron/pytest-parallel/issues/99
> [3] https://pypi.org/project/pytest-parallel/
> [4] https://github.com/browsertron/pytest-parallel/blob/master/tox.ini
> [5]
> https://github.com/browsertron/pytest-parallel/blob/master/README.md
> [6] https://github.com/browsertron/pytest-parallel/blob/master/LICENSE
> [7] https://github.com/browsertron/pytest-parallel/issues
>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 6.2.5

[Bruno Oliveira]

pytest 6.2.5 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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Anthony Sottile
* Bruno Oliveira
* Brylie Christopher Oxley
* Daniel Asztalos
* Florian Bruhin
* Jason Haugen
* MapleCCC
* Michał Górny
* Miro Hrončok
* Ran Benita
* Ronny Pfannschmidt
* Sylvain Bellemare
* Thomas Güttler


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Console folding

[Bruno Oliveira]

Hi Jeff,

That seems really useful, however it would require pytest's output to
become interactive, which would be a separate application I believe. This
certainly seems possible to implement as a plugin, perhaps using Rich?
Anyway that is a neat idea.

Cheers,
Bruno.

On Thu, Jul 1, 2021 at 6:20 AM Jeff Wright  wrote:

> Hello,
>
> I am doing some investigation into the possibility of implementing a
> 'folding' capability for Pytest's console output, and wanted to ask here
> about the feasibility of this idea. My main motivator is the fact that, in
> the face of multiple test failures, and with the default console behavior
> in place, the output can span many pages, requiring the tester to scroll
> back and hunt for the first failed test in the run. It is easy to get lost,
> and hard to pinpoint precisely where things started to go wrong.
>
> So I thought it would be helpful to have a capability that implements some
> sort of console 'folding', such that all the detailed Pytest console
> content is still available, just hidden by default - yet still able to be
> expanded in some way with operator interaction. [I don't know yet if
> "operator interaction" would be done with keyboard, mouse, or what.] I do
> know that Pytest already allows changing the level of verbosity, traceback
> info, etc. I am also aware of the pytest-html plugin, which is pretty much
> exactly what I am looking for, just in-console.
>
> Would appreciate some comments/advice...is this even do-able? I can't be
> the first person to dream of such a thing!
>
> Thanks, Jeff
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Pytest Dev Team Joining Request: pytest-mimesis

[Bruno Oliveira]

Invitation sent!

Cheers,
Bruno

On Thu, May 6, 2021 at 8:43 AM Likid  wrote:

> Yes, it is. Thanks you very much!
>
> On Thu, May 6, 2021 at 1:48 PM Bruno Oliveira 
> wrote:
>
>> Hi Isaak!
>>
>> As the author of pytest-mimesis, you are certainly welcome to join the
>> organization. Is your GitHub handle lk-geimfari?
>>
>> Cheers,
>>
>> On Wed, May 5, 2021 at 7:59 PM Likid  wrote:
>>
>>> Hi! My name is Isaak. I’m the author of Mimesis
>>> <https://github.com/lk-geimfari/mimesis> and
>>> https://github.com/pytest-dev/pytest-mimesis. I would like to join
>>> pytest-dev organization on Github, so I can work on pytest-mimesis
>>> directly. Also, I would like to contribute to other pytest plugins.
>>>
>>> As I know, anyone who contributed to pytest can join the dev team
>>> <https://docs.pytest.org/en/6.2.x/contributing.html#joining-the-development-team>,
>>> so I hope I can do it too.
>>>
>>> Thank you all!
>>> ___
>>> pytest-dev mailing list
>>> pytest-dev@python.org
>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>
>>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Pytest Dev Team Joining Request: pytest-mimesis

[Bruno Oliveira]

Hi Isaak!

As the author of pytest-mimesis, you are certainly welcome to join the
organization. Is your GitHub handle lk-geimfari?

Cheers,

On Wed, May 5, 2021 at 7:59 PM Likid  wrote:

> Hi! My name is Isaak. I’m the author of Mimesis
>  and
> https://github.com/pytest-dev/pytest-mimesis. I would like to join
> pytest-dev organization on Github, so I can work on pytest-mimesis
> directly. Also, I would like to contribute to other pytest plugins.
>
> As I know, anyone who contributed to pytest can join the dev team
> ,
> so I hope I can do it too.
>
> Thank you all!
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] How can I suppress cleanups when a test fails

[Bruno Oliveira]

Hi Eliot,

The only way to detect failures is using the pytest_runtest_logreport hook,
where you will obtain the test report for each test during each phase
(setup/call/teardown). You will need to store that somewhere so you can
reuse it later, possibly in a global variable or in self if you implement a
plugin class and register it during pytest_configure.

Here’s the example using a global variable, and printing the failed nodes
at the end of the session:

failed_tests = []
def pytest_runtest_logreport(report):
if report.outcome == "failed":
failed_tests.append(report.nodeid)
def pytest_terminal_summary(terminalreporter):
terminalreporter.section("my custom report")
terminalreporter.line(f"detected {len(failed_tests)} failures")

You can read more about hooks here:
https://docs.pytest.org/en/stable/writing_plugins.html#writing-hook-functions

Hope this helps,
Bruno.

On Thu, Apr 15, 2021 at 7:17 PM Eliot, Christopher <
christopher.el...@nagrastar.com> wrote:

> Thank you again.  What I really want is a way to ask Pytest, from inside a
> fixture or other python class, “hey Pytest, have you encountered any
> assertion failures during this session?”
>
>
>
> Topher Eliot
>
>
>
> *From:* Ronny Pfannschmidt 
> *Sent:* Thursday, April 15, 2021 3:05 PM
> *To:* Eliot, Christopher ;
> pytest-dev@python.org
> *Subject:* Re: [pytest-dev] How can I suppress cleanups when a test fails
>
>
>
> in case you use a orm/abstraction layer, sqlite in a tmpdir can be a
> wonderful companion
>
> in case you use another db, you can actually have failures do a db/data
> dump if you like,
>
> unfortunately i'm not aware of a tmp_path alike db setup/teardown tool
>
> --Ronny
>
> Am 15.04.21 um 23:00 schrieb Eliot, Christopher:
>
> Thank you.  This might be helpful, but I also have other resources that
> are not files that I would like to selectively clean up or not.  These
> resources are in a relational DB, not a file system.  And no, I can’t just
> wrap everything in a big transaction and then roll it back, unfortunately.
>
>
>
> Topher Eliot
>
>
>
> *From:* Ronny Pfannschmidt 
> 
>
> Hi Christopher,
>
> if you use the tmpdir/tmp_path fixtures pytest provides,
> just don't do additional cleanup, pytest keeps the last 3 basetemps around
> precisely for that use-case and drops older ones
>
> -- Ronny
>
> Am 15.04.21 um 21:56 schrieb Eliot, Christopher:
>
> My test suit generates some intermediate files and other resources which
> typically would be deleted upon termination of the test.  However, if there
> is a failure, I would like to leave them in place to help in diagnosing the
> failure.
>
>
>
> Is there a clean way to do this?
>
>
>
> I’m already using a fixture to do cleanup, so I’m prepared to use some
> aspect of the fixture if that’s appropriate.
>
>
>
> Thanks,
>
> Topher Eliot
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] autospec for monkeypatch

[Bruno Oliveira]

> there is no option to only accept existing keys.

I'm not sure what they mean... there's a `raising` keyword argument, 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:
>
> *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*
> *Reply-To:* dimitri.blyu...@gmail.com
>
> Name: Dimitri Blyumin
> Email: dimitri.blyu...@gmail.com
> Twitter:
> Website:
>
> Hi Brian,
> I'm going through your excellent "Python Testing with pytest" book, and
> came across this potential scenario in monkeypatching: if we use setitem
> and misspell the key - it will create a new key:value and will leave the
> original one as is, no KeyError or warning.
> Looking at the docs - there is no option to only accept existing keys.
> I think this can be dangerous in some cases when the user expects a value
> to be patched, and it is not, e.g. change environment in the config dict
> from PRD to DEV.
> Did you encounter this and is there a way to ensure that only existing
> keys are used in patching?
>
>
> --
> Fireside Labs, LLC (http://fireside.fm/)
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Transfer of pytest-order to pytest-dev

[Bruno Oliveira]

Folks,

Anybody opposes this? We need two +1 from core maintainers to move this
forward.

Cheers,
Bruno

On Tue, Mar 2, 2021 at 9:06 PM Bruno Oliveira  wrote:

> Hi Hansemrbean,
>
> As I wrote in the issues themselves, +1 from me.
>
> Thanks for stepping up!
>
> Cheers,
> Bruno.
>
> On Tue, Mar 2, 2021 at 5:51 PM hansemrbean via pytest-dev <
> pytest-dev@python.org> wrote:
>
>> pytest-order (https://github.com/mrbean-bremen/pytest-order) is a fork
>> of pytest-ordering (https://github.com/ftobia/pytest-ordering), which is
>> no longer maintained. The plugin allows ordering tests ordinally and
>> relatively to each other.
>>
>> I made the fork to be able to integrate proposed changes, to adapt it to
>> current Python/pytest versions, and to be able to move forward with the
>> project. As discussed in the issues mentioned below, I want to  transfer
>> it to pytest-dev to ensure continued maintenance. The transfer will be
>> handled in https://github.com/pytest-dev/meta/issues/7.
>>
>> For reference see also
>> https://github.com/ftobia/pytest-ordering/issues/32 and
>> https://github.com/mrbean-bremen/pytest-order/issues/4.
>>
>> Thanks
>>
>>
>> --
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Transfer of pytest-order to pytest-dev

[Bruno Oliveira]

Hi Hansemrbean,

As I wrote in the issues themselves, +1 from me.

Thanks for stepping up!

Cheers,
Bruno.

On Tue, Mar 2, 2021 at 5:51 PM hansemrbean via pytest-dev <
pytest-dev@python.org> wrote:

> pytest-order (https://github.com/mrbean-bremen/pytest-order) is a fork
> of pytest-ordering (https://github.com/ftobia/pytest-ordering), which is
> no longer maintained. The plugin allows ordering tests ordinally and
> relatively to each other.
>
> I made the fork to be able to integrate proposed changes, to adapt it to
> current Python/pytest versions, and to be able to move forward with the
> project. As discussed in the issues mentioned below, I want to  transfer
> it to pytest-dev to ensure continued maintenance. The transfer will be
> handled in https://github.com/pytest-dev/meta/issues/7.
>
> For reference see also
> https://github.com/ftobia/pytest-ordering/issues/32 and
> https://github.com/mrbean-bremen/pytest-order/issues/4.
>
> Thanks
>
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest documentation

[Bruno Oliveira]

Hi Daniele,

On Sat, Feb 27, 2021 at 9:26 AM Daniele Procida  wrote:

> As you may remember, back in 2017 at EuroPython in Rimini I made an
> attempt to restructure pytest's documentation, according to the principles
> in https://documentation.divio.com. See
> https://github.com/pytest-dev/pytest/issues/4119 and <
> https://github.com/pytest-dev/pytest/compare/master...evildmp:documentation-restructure
> >.
>
> It wasn't a success, and that was because I tried to do too much at once
> when too much else was going on at the same time.
>

Understandable, it is hard to apply large changes over a long period of
time, especially documentation which has small additions/changes all the
time, which causes conflicts in the long term. Also, life happens.

I'd like to have another attempt, but to approach it in a different way
> that has worked well for me since then.
>
> Rather than work on a large, monolithic reorganisation as I tried before,
> I would like to do it in very small commits and cycles, that can quickly be
> checked, approved and merged, over a period of a few weeks.
>

That sounds good to me.

Are the small changes self-contained? If so, I think they can target the
master branch as usual with other PRs.

If however the changes are just part of an overall redesign, where it only
makes sense to publish them to users once the overall redesign is complete,
we can have a separate branch in the repository, like before.

Would you be interested in my tackling this again? I believe that this
> approach will be successful in a way that it wasn't last time.
>

>From my part, definitely. I really liked the direction that redesign was
going.

To help make it work, I would need to be able to rely on very short
> review/merge cycles, which I know is asking a lot in a project like this.
> On the other hand, each proposed change will typically be very small and
> easy to review. In fact some of them will likely seem quite trivial or
> banal in content, but if you can put up with that during the process, it's
> part of the approach.
>

Overall our review response is quick, usually within 1-2 days (if not a few
hours). What do you think would be required for this work?

I will use the work as an example for my talk in April at Write the Docs,
> https://www.writethedocs.org/conf/portland/2021/speakers/#speaker-daniele-procida,
> so that also gives you an idea of when I expect the process to be largely
> complete (I will also discuss my original attempt, and why it failed).
>
> I understand if you feel that this would require too much effort from the
> team to be worthwhile, but if you think it could be a good idea, I'd be
> happy to outline what I have in mind in more detail.
>

I definitely think it would be a good idea, but I'm interested to hear what
the other maintainers think as well.

Thanks for offering to contribute again!

Cheers,
Bruno.
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest-6.2.2

[Bruno Oliveira]

pytest 6.2.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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Adam Johnson
* Bruno Oliveira
* Chris NeJame
* Ran Benita


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Hi James,

What I suggest you do in your case is to decouple your code from the
fixture, so if you have something like this today:

@pytest.fixture(scope="module")
def my_work_reqs():
# some
# complicated
# setup
# code

yield  x # some result

# some
# complicated
# teardown
# code

You can write instead:


@contextmanager
def handle_work_reqs():
# some
# complicated
# setup
# code
try:
yield x # some result
finally:
# some
# complicated
# teardown
# code

@pytest.fixture(scope="module")
def my_work_reqs():
with handle_work_reqs() as x:
yield x

Now you can test handle_work_reqs normally, as it is not tied to the pytest
framework.

I like this approach in general, decoupling custom code from a framework is
a great way to make it easier to test.

HTH,
Bruno.

On Wed, Jan 6, 2021 at 2:37 PM James Cooke  wrote:

> Hi all,
>
> It's been a while since I've had to write a complicated and robust pytest
> fixture and I'm struggling with testing the teardown / finalisation code.
>
> Instead of boring you with the [my-work-project] requirements of cleaning
> up GCS after tests, I'll refer to the fixture in the docs
> https://docs.pytest.org/en/stable/fixture.html#fixture-finalization-executing-teardown-code
> :
>
> @pytest.fixture(scope="module")
> def smtp_connection():
> smtp_connection = smtplib.SMTP("smtp.gmail.com", 587, timeout=5)
> yield smtp_connection  # provide the fixture value
> print("teardown smtp")
> smtp_connection.close()
>
> My (very old) usual strategy for testing teardown of a fixture that uses
> `yield` would be:
>
> * Start test
>
> - Instantiate the fixture.
>
> - Manipulate the instance with `next()` to trigger the teardown.
>
> - Ensure that teardown was successful - in this case assert that the
> SMTP connection returned when the fixture was instantiated was closed
> successfully.
>
> Given that since v4.1 (https://github.com/pytest-dev/pytest/issues/4545),
> the arrangement step of "Instantiate the fixture" does not work, could
> someone point me at the recommended method of testing fixture teardown?
>
> I would like to ensure that teardown is resilient and can resolve multiple
> conditions that can happen in [my-work-project]'s test suite. I can see
> that there are multiple tests on fixtures in
> https://github.com/pytest-dev/pytest/blob/48c9a96a03261e7cfa5aad0367a9186d9032904a/testing/python/fixtures.py
> , are there any preferred / recommended / efficient methods in this file?
> Alternatively, is there a way to by-pass the fixture wrapping that happens
> that prevents it being callable? Should I be using
> `smtp_connection.__pytest_wrapped__.obj()` to instantiate? (this seems bad)
>
> Any pointers / suggestions would be great.
>
> Thanks,
>
> James
>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 6.2.1

[Bruno Oliveira]

pytest 6.2.1 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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Bruno Oliveira
* Jakob van Santen
* Ran Benita


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Running doctest for the certain function

[Bruno Oliveira]

Hi Ilya,

That's the current behavior, there are no command-line/syntax to select
doctests inside files.

Cheers,
Bruno.

On Sun, Dec 13, 2020 at 8:37 PM Ilya Kazakevich via pytest-dev <
pytest-dev@python.org> wrote:

> Hello.
>
> I have some function with doctest in a file called "spam.py"
> ```
> def egg():
> """
> >>> egg()
> True
> """
>
> return True
>   ```
>
>
> I want to run doctest using pytest:
>
> ``pytest spam.py::egg --doctest-modules``
>
> But it doesn't work:
> ==no tests ran in 0.05s ==
>
> It seems that I can't run doctest for any particular function: I can run
> it only for the whole directory.
>
> Is this behavior intentional or a bug?
>
> Thank you.
>
> Ilya.
>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 6.1.2 released

[Bruno Oliveira]

pytest 6.1.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/stable/changelog.html.

Thanks to all of the contributors to this release:

* Bruno Oliveira
* Manuel Mariñez
* Ran Benita
* Vasilis Gerakaris
* William Jamir Silva


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] How do plugins support multiple pytest versions?

[Bruno Oliveira]

Hey Brian,


On Tue, Oct 6, 2020 at 1:55 PM Brian Okken  wrote:

> 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 behavior is close enough to work as a
> drop in replacement.
>
> But even if it is, switching to the new api makes the plugin only work on
> pytest 6.0 and above.
>
> Is it recommended that plugin authors try to force users to always use the
> latest pytest?
>
What if they want to support older versions also?
>
> Is there a recommended way to say this?
>
> if  pytest version < 6, use one hook
> else use new hook
>
>
I believe it really depends on the plugin and how many users you have.
Certainly only supporting the latest pytest version is easier,
but if you must support older versions, then checking the version to decide
which hooks to implement is doable.

An alternative is to check if the new hook exists, like how we used to do
in pytest-xdist:

https://github.com/pytest-dev/pytest-xdist/blob/7bf654775dcd2fef9c0ebafbea982b7d180b740e/src/xdist/remote.py#L142-L164

Where we implement one hook or the other, giving preference to the new hook
when available.

Cheers,
Bruno.



>
> Thanks,
> Brian
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Using meta project for organization wide issues

[Bruno Oliveira]

Hi everyone,

The Discussions feature is now enabled.

Let's see how best we can use this feature to declutter the issue tracker
if possible, and create a good knowledge base of problems/solutions.

Cheers,

On Wed, Sep 9, 2020 at 8:32 AM Bruno Oliveira  wrote:

> Thanks Sorin for bringing this up.
>
> I've posted a request to enable the Discussions feature for
> pytest-dev/pytest:
> https://github.community/t/can-one-apply-for-github-discussions-beta/121120/162?u=nicoddemus
>
> Cheers,
> Bruno.
>
> On Tue, Sep 8, 2020 at 11:08 AM Sorin Sbarnea  wrote:
>
>> My intent was to separate organization threads from the development ones,
>> not to deprecate the mailing list.
>>
>> I do not think that an issue tracker is good for **discussions** as in
>> open-ended subjects, or even for support. In fact using the issue tracker
>> for user support is really bad as it make maintenance much harder.
>>
>> Still, there is something new from github called discussions which is a
>> very basic forum directly integrated into github.
>>
>> You can see it as
>> https://github.com/ansible-community/molecule/discussions -- not very
>> active but functional.
>>
>> Discussions are in private beta, and we need to ask github to enable
>> them.
>>
>> If anyone wants to enable it for "pytest", I could try to pull some
>> strings. If desired, an org/repo admin should ask for it at
>> https://github.community/t/can-one-apply-for-github-discussions-beta/121120
>>
>>
>> > On 8 Sep 2020, at 14:54, Arseniy Antonov 
>> wrote:
>> >
>> > Hi Sorin,
>> > So basically you want to move all projects related discussions from
>> maillists to the github issues - did I get you correct?  If the answer is
>> yes then from my perspective it's a really nice idea.
>> > Also a lot of communities have #slack accounts - have you ever thought
>> about the slack/(any other messenger) group for pytest community?
>> >
>> > вт, 8 сент. 2020 г. в 16:07, Sorin Sbarnea :
>> > About two weeks ago I created the https://github.com/pytest-dev/meta
>> project with the hope of being used for tracking organization wide issues
>> (and avoid having to pollute our main pytest project).
>> >
>> > I seen use of "meta" on many github organizations for the same purpose,
>> "stuff" that is unrelated to the code of a specific repository. I hope it
>> will become popular. I do also see other benefits as used of a mailing list
>> sets a higher barrier for people that are not yet fully dedicated (we do
>> all know experienced the "Ahh not another ML!" sensation).
>> >
>> > Early today I also added the first ticket, the proposal for adoption of
>> the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1
>> and comment there.
>> >
>> > Cheers,
>> > Sorin
>> >
>> > ___
>> > pytest-dev mailing list
>> > pytest-dev@python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>> >
>> >
>> > --
>> > --
>> > Regards.
>> > Arseny Antonov
>>
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Using meta project for organization wide issues

[Bruno Oliveira]

Thanks Sorin for bringing this up.

I've posted a request to enable the Discussions feature for
pytest-dev/pytest:
https://github.community/t/can-one-apply-for-github-discussions-beta/121120/162?u=nicoddemus

Cheers,
Bruno.

On Tue, Sep 8, 2020 at 11:08 AM Sorin Sbarnea  wrote:

> My intent was to separate organization threads from the development ones,
> not to deprecate the mailing list.
>
> I do not think that an issue tracker is good for **discussions** as in
> open-ended subjects, or even for support. In fact using the issue tracker
> for user support is really bad as it make maintenance much harder.
>
> Still, there is something new from github called discussions which is a
> very basic forum directly integrated into github.
>
> You can see it as
> https://github.com/ansible-community/molecule/discussions -- not very
> active but functional.
>
> Discussions are in private beta, and we need to ask github to enable them.
>
> If anyone wants to enable it for "pytest", I could try to pull some
> strings. If desired, an org/repo admin should ask for it at
> https://github.community/t/can-one-apply-for-github-discussions-beta/121120
>
>
> > On 8 Sep 2020, at 14:54, Arseniy Antonov 
> wrote:
> >
> > Hi Sorin,
> > So basically you want to move all projects related discussions from
> maillists to the github issues - did I get you correct?  If the answer is
> yes then from my perspective it's a really nice idea.
> > Also a lot of communities have #slack accounts - have you ever thought
> about the slack/(any other messenger) group for pytest community?
> >
> > вт, 8 сент. 2020 г. в 16:07, Sorin Sbarnea :
> > About two weeks ago I created the https://github.com/pytest-dev/meta
> project with the hope of being used for tracking organization wide issues
> (and avoid having to pollute our main pytest project).
> >
> > I seen use of "meta" on many github organizations for the same purpose,
> "stuff" that is unrelated to the code of a specific repository. I hope it
> will become popular. I do also see other benefits as used of a mailing list
> sets a higher barrier for people that are not yet fully dedicated (we do
> all know experienced the "Ahh not another ML!" sensation).
> >
> > Early today I also added the first ticket, the proposal for adoption of
> the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1 and
> comment there.
> >
> > Cheers,
> > Sorin
> >
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
> >
> > --
> > --
> > Regards.
> > Arseny Antonov
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

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/
> >> https://pypi.org/project/pytest-molecule/
> >
> > +1 from me.
> >
> > I'm assuming Floris also agrees, so feel free to transfer the
> repositories
> > to me to conclude the transfer.
>
> Oh, I thought I already saw the repository transfer which is why I
> didn't add a +1.  But sure, :)
>

Oh wait, my bad, completely missed the Subject which clearly states
pytest-html, hehehe.

Cheers,
Bruno
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Hi all,

On Sat, Aug 15, 2020 at 2:05 PM Sorin Sbarnea  wrote:

> I would like to transfer two pytest plugins (MIT) that I wrote and
> maintain to pytest-dev organization.
>
> My main goals being:
> - assure their long term maintenance
> - adopt similar testing methods
> - improve cross plugin testing (also to implement pre-release testing to
> avoid post-release conflicts)
> - improve discoverability of the plugins
>
>
> https://pypi.org/project/pytest-plus/
> https://pypi.org/project/pytest-molecule/



+1 from me.

I'm assuming Floris also agrees, so feel free to transfer the repositories
to me to conclude the transfer.

Cheers,
Bruno

I think that the projects already pass the requirements from
> https://docs.pytest.org/en/stable/contributing.html#submitting-plugins-to-pytest-dev
> -- because they were creating with shared ownership from start.
>
> I may note that the list of requirements is a little bit outdated, but I
> think nobody bothered with minor details like replacing README.txt with
> README.(txt|md|rst), or mentioning that required metadata can be better
> stored in setup.cfg instead of setup.py, which can even be missing (at
> least in theory).
>
>
> Both plugins are very simple and they do not have any special
> runtime/testing requirements. They will both use github-actions (the second
> one is tested with zuul-ci now, but I can switch it very easy).
>
>
> Cheers,
> Sorin Sbarnea
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest 6.0.1

[Bruno Oliveira]

Ahh sorry, the correct link is:

https://docs.pytest.org/en/stable/changelog.html

This has been fixed in master, but not ported to the 6.0.x branch yet. Will
fix it.

Thanks,
Bruno

On Thu, Jul 30, 2020 at 11:20 AM Thomas Grainger  wrote:

> I can't see a 6.0.1 changelog at that link
>
> On Thu, Jul 30, 2020, 13:50 Bruno Oliveira  wrote:
>
>> pytest 6.0.1 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:
>>
>> * Bruno Oliveira
>> * Mattreex
>> * Ran Benita
>> * hp310780
>>
>>
>> Happy testing,
>> The pytest Development Team
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 6.0.1

[Bruno Oliveira]

pytest 6.0.1 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:

* Bruno Oliveira
* Mattreex
* Ran Benita
* hp310780


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 6.0.0 released!

[Bruno Oliveira]

The pytest team is proud to announce the 6.0.0 release!

pytest is a mature Python testing tool with more than 2000 tests
against itself, passing on many different interpreters and platforms.

This release contains a bunch of new goodies such as typing annotations,
pyproject.toml, new hooks, and new command-line flags.

CHANGELOG:

https://docs.pytest.org/en/stable/changelog.html

For complete documentation, please visit:

https://docs.pytest.org/en/stable/

As usual, you can upgrade from PyPI via:

pip install -U pytest

Thanks to all users who have tested the 6.0.0rc1 release, it really helped
us out nail down a few problems before the final release.

Also many thanks to all contributors, among them:

* Alfredo Deza
* Andreas Maier
* Andrew
* Anthony Sottile
* ArtyomKaltovich
* Arvin Firouzi
* Bruno Oliveira
* Claire Cecil
* Curt J. Sampson
* Daniel
* Daniel Hahler
* Danny Sepler
* David Diaz Barquero
* Debi Mishra
* earonesty
* Fabio Zadrozny
* Felix Nieuwenhuizen
* Florian Bruhin
* Florian Dahlitz
* Garrett Thomas
* gaurav dhameeja
* gdhameeja
* Gleb Nikonorov
* Hugo van Kemenade
* Hunter Richards
* ibriquem
* Katarzyna Król
* Katrin Leinweber
* Kelton Bassingthwaite
* Keri Volans
* Kostis Anagnostopoulos
* Lewis Belcher
* Lewis Cowles
* Lukas Geiger
* Martin Michlmayr
* Mattwmaster58
* Maximilian Cosmo Sitter
* mcsitter
* Miro Hrončok
* Nikolay Kondratyev
* Pavel Karateev
* Paweł Wilczyński
* piotrhm
* Prashant Anand
* Ram Rachum
* Ran Benita
* Ronny Pfannschmidt
* Ruaridh Williamson
* Simon K
* smarie
* symonk
* Tim Hoffmann
* Tor Colvin
* Vlad-Radz
* Xinbin Huang
* xuiqzy
* Zac Hatfield-Dodds

Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] my limited/reduced availability until at least mid-september/october

[Bruno Oliveira]

Hi Ronny,

Thanks for the heads up! Please make sure to take the time you need to care
for your family, we are always grateful for all the work you do in pytest +
the ecosystem.

Cheers,
Bruno

On Tue, Jul 21, 2020 at 6:07 PM Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:

> Hi everyone,
>
> i just wanted to inform everyone, that due to corona and my specific
> family situation,
> we are still in a mitigation situation.
>
> This is one of the key factors of my reduced engagement with pytest and
> the community.
>
> By September we will move into into a new flat and get daycare for the
> toddler again.
> Once we are settled after that and had some time to relax+reorient i'll
> pick up more pytest joy again.
>
> Regards and stay healthy
> Ronny
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 6.0.0rc1 released

[Bruno Oliveira]

pytest 6.0.0rc1 has just been released to PyPI.

This is a prerelease to help identify any issues before the final 6.0.0.
Please use this version to run your test suite and report any problems!

To upgrade:

  pip install --upgrade --pre 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:

* Alfredo Deza
* Andreas Maier
* Andrew
* Anthony Sottile
* ArtyomKaltovich
* Bruno Oliveira
* Claire Cecil
* Curt J. Sampson
* Daniel
* Daniel Hahler
* Danny Sepler
* David Diaz Barquero
* Fabio Zadrozny
* Felix Nieuwenhuizen
* Florian Bruhin
* Florian Dahlitz
* Gleb Nikonorov
* Hugo van Kemenade
* Hunter Richards
* Katarzyna Król
* Katrin Leinweber
* Keri Volans
* Lewis Belcher
* Lukas Geiger
* Martin Michlmayr
* Mattwmaster58
* Maximilian Cosmo Sitter
* Nikolay Kondratyev
* Pavel Karateev
* Paweł Wilczyński
* Prashant Anand
* Ram Rachum
* Ran Benita
* Ronny Pfannschmidt
* Ruaridh Williamson
* Simon K
* Tim Hoffmann
* Tor Colvin
* Vlad-Radz
* Xinbin Huang
* Zac Hatfield-Dodds
* earonesty
* gaurav dhameeja
* gdhameeja
* ibriquem
* mcsitter
* piotrhm
* smarie
* symonk
* xuiqzy


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] hardcode 4.x mid-2020 EOL

[Bruno Oliveira]

Hi Thomas,

Thanks for bringing this up! Hardcoding the date for 4.6 EOL is something
we should discuss.

So far we have had a few releases since the beginning of the year: January,
May and June, with contributions from the community.

Given our overhead is relatively small (review merge a PR and make the
release), and if a user is going through the trouble of contributing a fix
it probably means it blocks/bother them enough to care to make a PR, I
personally don't mind extending our commitment of making new 4.6 releases
contributions until the end of the year, and stating that officially.

I would like to hear what others think about this though.

Cheers,



On Wed, Jul 1, 2020 at 7:49 AM Thomas Grainger  wrote:

> By most calculations mid-2020 has now passed,
>
> I propose hardcoding mid-2020 to some date in the (very) near future,
> eg 2020-08-01
>
> Thomas Grainger
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 4.6.11

[Bruno Oliveira]

pytest 4.6.11 has just been released to PyPI.

pytest 4.6 is the last version that still supports Python 2, being
supported by patches from the community. To upgrade:

pip install --upgrade pytest

The full changelog is available at
https://docs.pytest.org/en/4.6.x/changelog.html

Thanks to all who contributed to this release, among them:

* Anthony Sottile
* Bruno Oliveira
* Sviatoslav Sydorenko

Happy testing, The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.4.3

[Bruno Oliveira]

pytest 5.4.3 has just been released to PyPI.

This is a bug-fix release, being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The full changelog is available at
https://docs.pytest.org/en/latest/changelog.html.

Thanks to all who contributed to this release, among them:

* Anthony Sottile
* Bruno Oliveira
* Ran Benita
* Tor Colvin


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.4.2

[Bruno Oliveira]

pytest 5.4.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
* Daniel Hahler
* Ran Benita
* Ronny Pfannschmidt


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] New home and maintainer for pytest-describe?

[Bruno Oliveira]

+1 as well :)

On Sun, Apr 5, 2020 at 9:38 AM Floris Bruynooghe  wrote:

> Hi Christoph,
>
> On Fri 03 Apr 2020 at 20:25 +0200, Christoph Zwerschke wrote:
>
> > The author of pytest-describe, a pytest plugin for Jasmine-style nesting
> > of test functions, is currently looking for a new maintainer.
> >
> > jacebrowning and I already volunteered. If anybody else is interested in
> > maintaining that project, please let us know.
>
> Thanks for stepping up to maintain a pytest plugin!
>
> > Als, we would like to move the plugin repository (currently at
> > https://github.com/ropez/pytest-describe) to the pytest-dev
> organization
> > (https://github.com/pytest-dev). Who would be a good contact person in
> > the pytest-dev organization to help with such a transfer?
>
> Sure, I had a look at it seems like you tick all the boxes from
>
> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
> to transfer the repo.  Just make sure both of you have the required
> pypi.org admin rights for the package.
>
> So from me that's a +1 to move it.  We just need another +1 from
> someone.
>
> If we get that I'm happy to do the transferring as detailed in the link
> above.  Just ping me when it gets to that stage.
>
> Cheers,
> Floris
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Fwd: Continuing on failures

[Bruno Oliveira]

Hi Maximilian,

On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos 
wrote:

>
> To prefix: as a long time user and evangelizer of pytest, a big thank you
> for the superb tool.
>

Thanks for the kind words, we appreciate it.


> As per that README, it only works on the first failure, because the test
> doesn't continue execution beyond that. *Is there any way of allowing
> execution to continue, without ripping up the internals of pytest?* My
> prior is "no", since the assertion rewrite still retains an assertion, and
> there's no hook for changing that.
>

Not at the moment I'm afraid.

I think it should be possible to implement a hook that transforms the AST,
which our rewriter would then call. I think, with this hook in place, you
would be able to rewrite assert statements into a function call of your
plugin, which would then be free to do whatever it wanted. If you are
interested, I suggest writing up a proposal in the issue tracker so it can
be discussed.

Cheers,
Bruno


> Ref: a similar question I asked @okken
> https://github.com/okken/pytest-check/issues/32
>
> Thank you,
> Max
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.4.1 released!

[Bruno Oliveira]

pytest 5.4.1 has just been released to PyPI.

This is a bug-fix release, fixing a regression discovered in 5.4.0, 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


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Proposal: Elevating Ran Benita/@bluetech from Contributor to Core

[Bruno Oliveira]

Hi everyone,

I think this is unanimous then, I've added bluetech to the Core team.

Cheers,
Bruno

On Sun, Mar 8, 2020 at 4:51 PM Tyler Goodlet  wrote:

> +1 from myself as well considering the couple contribs to pluggy :)
>
> - goodboy
>
> On Sat, Mar 7, 2020 at 1:55 PM Ronny Pfannschmidt
>  wrote:
> >
> > Hi everyone,
> >
> > over the last few months Ran demonstrated both excellent communication
> > and contribution.
> > I believe Ran would make a great addition to the Core team.
> >
> > So after reaching out to Ran to check if that's ok,
> > I'm asking the rest us to formalize addition..
> >
> > -- Ronny
> >
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Proposal: Elevating Ran Benita/@bluetech from Contributor to Core

[Bruno Oliveira]

Definitely +1

On Sat, Mar 7, 2020 at 3:55 PM Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:

> Hi everyone,
>
> over the last few months Ran demonstrated both excellent communication
> and contribution.
> I believe Ran would make a great addition to the Core team.
>
> So after reaching out to Ran to check if that's ok,
> I'm asking the rest us to formalize addition..
>
> -- Ronny
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.3.4

[Bruno Oliveira]

pytest 5.3.4 has just been released to PyPI.

This is release reverts a regression introduced by a bug-fix in 5.3.3, all
users affected should 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
* Ran Benita


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.3.3

[Bruno Oliveira]

pytest 5.3.3 has just been released to PyPI.

This is a bug-fix release, being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The full changelog is available at
https://docs.pytest.org/en/latest/changelog.html.

Thanks to all who contributed to this release, among them:

* Adam Johnson
* Alexandre Mulatinho
* Anthony Sottile
* Bruno Oliveira
* Chris NeJame
* Daniel Hahler
* Hugo van Kemenade
* Marcelo Duarte Trevisani
* PaulC
* Ran Benita
* Ryan Barner
* Seth Junot
* marc


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest does not collect test-cases - what am I doing wrong?

[Bruno Oliveira]

Hi Hartmut.

Sure thing, thanks for creating the issue and maintaining PyInstaller. :)

(FWIW in case you didn't know already, we freeze pytest as part of our
suite using PyInstaller:
https://github.com/pytest-dev/pytest/blob/b91c721262a57ca265eace37daf79475abf4cd91/.github/workflows/main.yml#L86-L89
)

Cheers,
Bruno



On Thu, Jan 16, 2020 at 2:00 PM Hartmut Goebel 
wrote:

> Hi,
>
> Thanks you very much for evaluating this so quickly :-)
>
> I was able to work around the issue by uninstalling pytest-drop-dup-tests.
> Nevertheless I opens an issue there so this doesn't get lost.
>
> https://github.com/nicoddemus/pytest-drop-dup-tests/issues/3
>
> --
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel  | h.goe...@crazy-compilers.com   |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest does not collect test-cases - what am I doing wrong?

[Bruno Oliveira]

Hi!

Thanks for the branches, I managed to reproduce the issue but only after
installing the exact same versions of pytest, pluggy, and plugins.

The problem is the pytest-drop-dup-tests plugin, if I pass -p
no:drop-dup-tests, the test is collected and executed as normal.

If you really need to use pytest-drop-dup-tests, please create an issue
there and I will take a look later, otherwise just uninstalling is enough
for your example to work.

Cheers,

On Thu, Jan 16, 2020 at 11:38 AM Hartmut Goebel <
h.goe...@crazy-compilers.com> wrote:

> Hi Bruno,
>
> > But the instructions you wrote don’t fit the repository, so I suspect
> > you have changed the layout since writing your original email. Could
> > you please perhaps pushing to a branch
> Sorry, I wanted to list the files in a way easy to understand.
> Now the repo  contains two
> branches:
>
> 1. "one-level-less": test-cases are in src/pyi_hooksample/__pyinstaller
>
>pytest src/pyi_hooksample/__pyinstaller
>-> NO tests will be picked up
>
> 2. master: test-cases are in src/pyi_hooksample/__pyinstaller/t (mind
> the trailing t)
>
>pytest src/pyi_hooksample/__pyinstaller/t
>-> NO tests will be picked up
>
>pytest src/pyi_hooksample/__pyinstaller   # one level above the test
>-> NO tests will be picked up
>
> => When pointing pytest to the package containing the tests, they will
> NOT be picked up
>
> => When pointing pytest to the parent package the tests will be picked up
>
>
> (My aim is to have a layout like in "one-level-less" and point pytest to
> src/pyi_hooksample/__pyinstaller.)
>
> platform linux -- Python 3.7.5, pytest-5.0.1, py-1.8.0, pluggy-0.12.0
> plugins: cov-2.7.1, drop-dup-tests-0.1.0, forked-1.0.2, timeout-1.3.3,
> xdist-1.29.0
>
> --
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel  | h.goe...@crazy-compilers.com   |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest does not collect test-cases - what am I doing wrong?

[Bruno Oliveira]

Hi Harmut,

It works for me when I use your repository directly:

λ pip install pytest PyInstaller
λ python -m pytest src
 test session starts 
platform win32 -- Python 3.6.8, pytest-5.3.2, py-1.8.1, pluggy-0.13.1
rootdir: C:\Users\bruno\hooksample
collected 1 item

src\pyi_hooksample\__pyinstaller\t\test_hooksample_packaging.py . [100%]

= warnings summary ==
src/pyi_hooksample/__pyinstaller/t/test_hooksample_packaging.py::test_pyi_hooksample
  
C:\Users\bruno\hooksample\.env36\lib\site-packages\PyInstaller\lib\modulegraph\util.py:4:
DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
import imp

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=== 1 passed, 1 warning in 4.87s 

But the instructions you wrote don’t fit the repository, so I suspect you
have changed the layout since writing your original email. Could you please
perhaps pushing to a branch
the exact state of your instructions so I can try to reproduce the issue?
Thanks!

Cheers,
Bruno

On Thu, Jan 16, 2020 at 6:25 AM Hartmut Goebel 
wrote:

> Hi,
>
> my package layout follows the "Tests as part of application code" [1]:
>
> src/mypkg/__init__.py
> src/mypkg/app.py
> src/mypkg/test/__init__.py
> src/mypkg/test/test_hooksample_packaging.py
>
> where "__pyinstaller" contains the tests to be picked up.
>
> 1. When running "python3 -m pytest src/mypkg/test" NO tests will be
> collected.
>
> 2. I tried moving src/mypkg/test into src/mypkg/test/xxx (one level more):
>
> * When running "python3 -m pytest src/mypkg/test", tests will be
> picked up.
>
> * When running "python3 -m pytest src/mypkg/test/xxx" NO will be
> picked up.
>
> What am I going wrong here?
>
> Just in case: The actual repo can be found at
> .
>
> [1]
>
> http://doc.pytest.org/en/latest/goodpractices.html#tests-as-part-of-application-code
>
> --
>
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel  | h.goe...@crazy-compilers.com   |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Opinions on the looks of the pytest docs

[Bruno Oliveira]

Hi everyone,

I've tried to send a message here about the current looks of the pytest
documentation here, but due to image sizes it was blocked, so I opened an
issue instead:

https://github.com/pytest-dev/pytest/issues/6402

Everyone is welcome to join the discussion there.

Cheers,
Bruno
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] returning from my break and choosing my role

[Bruno Oliveira]

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 <
opensou...@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@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.3.2

[Bruno Oliveira]

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
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 4.6.7 released

[Bruno Oliveira]

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
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

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 <
> opensou...@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
> >> >>
> >> >> --
> >> >> m...@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@python.org
> >> >> https://mail.python.org/mailman/listinfo/pytest-dev
> >> > ___
> >> > pytest-dev mailing list
> >> > pytest-dev@python.org
> >> > https://mail.python.org/mailman/listinfo/pytest-dev
> >> ___
> >> pytest-dev mailing list
> >> pytest-dev@python.org
> >> https://mail.python.org/mailman/listinfo/pytest-dev
> >
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

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 <
opensou...@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
> >>
> >> --
> >> m...@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@python.org
> >> https://mail.python.org/mailman/listinfo/pytest-dev
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Hi Christoph,

On Wed, Dec 4, 2019 at 9:38 AM Christoph Buelter <
buelter.christ...@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
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Requesting a change of our deprecation policy and the potentially removal of the features branch

[Bruno Oliveira]

Hi everyone,

I'm also fine to discuss changes to our deprecation policy as Ronny is
suggesting.

Cheers,
Bruon

On Mon, Nov 25, 2019 at 12:02 PM Bruno Oliveira 
wrote:

> Hi Ronny,
>
> Thanks for writing up.
>
> Personally I'm tired of arguing for having the "features" branch around,
> which most core devs think it is not necessary, so I'm OK with us dropping
> it and just having a `master` branch, with each release being potentially a
> bugfix or a feature release.
>
> Cheers,
> Bruno
>
> On Sun, Nov 24, 2019 at 7:36 PM RonnyPfannschmidt <
> opensou...@ronnypfannschmidt.de> wrote:
>
>> Hi everyone,
>>
>> in the last few months i have tried to find a way to work with/around
>> our deprecation policy while detangleing Nodes (and something similar
>> will be required for fixtures as well).
>>
>> This process has been rather frustrating and time-eating so far,
>> additionally the changes (like for example node-from-parent) do not
>> nearly deliver as much value as i hoped it would.
>>
>> For me personally i arrived at the conclusion, that if the current
>> deprecation policy stays,
>> its no longer reasonable for me to spend time on trying to restructure
>> the entangled  internals of pytest.
>>
>> In addition, even when attempting to iterate this in small breaking
>> increments,
>> its abysmally ineffective from a feedback loop standpoint to have the
>> feature branch gate such changes for longer time-frames.
>>
>> As such i want to request that we enable pushing for "reasonably sized"
>> breaking changes way more often.
>>
>> (where reasonably sized means touches exposed internals/structure in
>> such a way that it wont affect normal  users, but might affect plugins
>> that are deeply involved)
>>
>> (examples of this are dropping support for the config/session parameters
>> for node constructors, changing the behavior of the node-id creation,
>> changing the config object initialization lifecycle/state  management).
>>
>>
>> And additionally i want to request dropping the feature branch mechanism
>> in order to get a much tighter feedback loop on the changes going in.
>>
>>
>> -- Ronny
>>
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Requesting a change of our deprecation policy and the potentially removal of the features branch

[Bruno Oliveira]

Hi Ronny,

Thanks for writing up.

Personally I'm tired of arguing for having the "features" branch around,
which most core devs think it is not necessary, so I'm OK with us dropping
it and just having a `master` branch, with each release being potentially a
bugfix or a feature release.

Cheers,
Bruno

On Sun, Nov 24, 2019 at 7:36 PM RonnyPfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:

> Hi everyone,
>
> in the last few months i have tried to find a way to work with/around
> our deprecation policy while detangleing Nodes (and something similar
> will be required for fixtures as well).
>
> This process has been rather frustrating and time-eating so far,
> additionally the changes (like for example node-from-parent) do not
> nearly deliver as much value as i hoped it would.
>
> For me personally i arrived at the conclusion, that if the current
> deprecation policy stays,
> its no longer reasonable for me to spend time on trying to restructure
> the entangled  internals of pytest.
>
> In addition, even when attempting to iterate this in small breaking
> increments,
> its abysmally ineffective from a feedback loop standpoint to have the
> feature branch gate such changes for longer time-frames.
>
> As such i want to request that we enable pushing for "reasonably sized"
> breaking changes way more often.
>
> (where reasonably sized means touches exposed internals/structure in
> such a way that it wont affect normal  users, but might affect plugins
> that are deeply involved)
>
> (examples of this are dropping support for the config/session parameters
> for node constructors, changing the behavior of the node-id creation,
> changing the config object initialization lifecycle/state  management).
>
>
> And additionally i want to request dropping the feature branch mechanism
> in order to get a much tighter feedback loop on the changes going in.
>
>
> -- Ronny
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.3.0

[Bruno Oliveira]

The pytest team is proud to announce the 5.3.0 release!

pytest is a mature Python testing tool with more than a 2000 tests
against itself, passing on many different interpreters and platforms.

This release contains a number of bugs fixes and improvements, so users are
encouraged
to take a look at the CHANGELOG:

https://docs.pytest.org/en/latest/changelog.html

For complete documentation, please visit:

https://docs.pytest.org/en/latest/

As usual, you can upgrade from pypi via:

pip install -U pytest

Thanks to all who contributed to this release, among them:

* AnjoMan
* Anthony Sottile
* Anton Lodder
* Bruno Oliveira
* Daniel Hahler
* Gregory Lee
* Josh Karpel
* JoshKarpel
* Joshua Storck
* Kale Kundert
* MarcoGorelli
* Michael Krebs
* NNRepos
* Ran Benita
* TH3CHARLie
* Tibor Arpas
* Zac Hatfield-Dodds
* 林玮


Happy testing,
The Pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Imran,

I've completed the move to pytest-dev and configured the teams. Please let
me know if anything is not working correctly for you.

Cheers,

On Mon, Nov 18, 2019 at 11:03 PM Imran M  wrote:

> @Florian, Yup! Sorry, should have clarified.
>
> @Bruno, transferred!
>
> Thanks guys! 落
>
> On Mon, Nov 18, 2019 at 4:51 AM Bruno Oliveira 
> wrote:
>
>>
>>
>> On Mon, Nov 18, 2019 at 7:04 AM Florian Bruhin 
>> wrote:
>>
>>> If so, +1 from me!
>>>
>>
>> +1 from me too. Feel free to transfer the repository to me or Florian so
>> we can complete the transferring process.
>>
>> Cheers,
>> Bruno
>>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

On Mon, Nov 18, 2019 at 7:04 AM Florian Bruhin  wrote:

> If so, +1 from me!
>

+1 from me too. Feel free to transfer the repository to me or Florian so we
can complete the transferring process.

Cheers,
Bruno
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.2.3

[Bruno Oliveira]

pytest 5.2.3 has just been released to PyPI.

This is a bug-fix release, being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The full changelog is available at
https://docs.pytest.org/en/latest/changelog.html.

Thanks to all who contributed to this release, among them:

* Anthony Sottile
* Brett Cannon
* Bruno Oliveira
* Daniel Hahler
* Daniil Galiev
* David Szotten
* Florian Bruhin
* Patrick Harmon
* Ran Benita
* Zac Hatfield-Dodds
* Zak Hassan


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.2.2

[Bruno Oliveira]

pytest 5.2.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:

* Albert Tugushev
* Andrzej Klajnert
* Anthony Sottile
* Bruno Oliveira
* Daniel Hahler
* Florian Bruhin
* Nattaphoom Chaipreecha
* Oliver Bestwalter
* Philipp Loose
* Ran Benita
* Victor Maryama
* Yoav Caspi


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Building the Rationale for upcoming changes in the node construction apis

[Bruno Oliveira]

Hi Ronny,

Thanks for all the hard work on this, I'm sure the final result will be as
good/valuable as all the internal mark refactoring.

Cheers,
Bruno

On Thu, Oct 24, 2019 at 6:20 PM RonnyPfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:

> Hi everyone,
>
> in https://github.com/pytest-dev/pytest/pull/5975 i have startet to
> prepare a POC with a ambitious goal,
> i want to remove much of the mind boggling smartness from the constructors
> and i want to streamline note constructors in order to reduce the
> coupling in the different types of nodes.
>
> The tight coupling and tricky construction of nodes has repeatedly
> foiled my attempts to refactor both fixtures/fixture caching and
> setupstate as well as
> actually introducing FunctionDefinition in the public api (and shifting
> generate_tests to it) and retiring Instance.
>
> So from my pov its  not sustainable to leave them be, as they prevent
> other required improvements.
> However as far as i can tell its next to impossible without breaking
> things.
>
> The Rough idea i have for iteratively solving it is to
>
> a) introduce Node.from_parent as the convention for node construction
> b) deprecate Node.__init__ being invoked outside of such a function
> c) destroy all the things and have a cupcake
>
> Whats needed in addition is a slightly  more eloquent version of the
> description for the  documentation.
>
> -- Ronny
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

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

[Bruno Oliveira]

Hi everyone,

For some time now execnet has been in maintenance only mode, and even so
very few people are willing to maintain it; lately just myself and I’m not
a good choice given that I don’t know the codebase at all, plus I have tons
on my plate already. This poses a problem because often we have bug reports
or feature requests in pytest-xdist which would require fixing or improving
execnet, and are currently left without solution.

Ronny and I have on occasion discussed the possibility of changing execnet‘s
backend , with the current contenders being multiprocessing for local
distribution and mitogen for remote distribution.

I would like to write down some thoughts and gather opinions from the
mailing list members.
multiprocessing

Aside from not needing to maintain execnet anymore, being able to use
multiprocessing would bring several benefits:

   -

   pytest -s would work just fine, because multiprocessing does not use
   stdout/stderr for communication. This is a often requested feature but
   which we can’t (with current expertise) implement on execnet.
   -

   It would automatically support anything that can be picked to be
   transmitted across the wire. Currently execnet does not support custom user
   types and some builtins (frozen sets for example).

Without execnet we would lose the ability of running the tests in different
interpreter versions, but I believe this has been supplanted by tox in the
ecosystem.
mitogen

Using mitogen for remote execution would provide automatic bootstrap of the
Python environment, which is not currently supported by xdist‘s ssh remote
execution, greatly limiting its usefulness in real-time scenarios.

This is Ronny’s idea and he can add more here if wanted.
pytest-xdist2?

All the changes mentioned above would break backward compatibility *hard*,
because details of the execnet implementation are currently exposed to
users in the command-line:

pytest -d --tx popen//python

And in several hooks:

def pytest_xdist_newgateway(gateway):
""" called on new raw gateway creation. """

(gateway is an execnet object)

To incorporate the new backends, we would need to severely break both
command-line and existing hooks. Given the level of breakage this could
cause, just bumping the major version in this case doesn’t seem enough, it
would be a disservice to users given that probably nobody pins pytest-xdist
to <=2, and it would break the world with hard to understand error messages
once a first major release was released.

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-xdist2 would, at first, only support local test distribution using
multiprocessing (-n flag), no new hooks, and no remote execution. I’ve made
a proof of concept here:

https://github.com/pytest-dev/pytest-xdist/pull/479

So it definitely seems possible. One immediate benefit is that the proof of
concept above supports pytest -s already, and can transfer anything that’s
pickled over the wire.

So I would like to know what people think of the above ideas, if they are
good/bad, and/or suggest alternatives that we are not seeing right now.

Ronny, please feel free to add to this email and correct anything I got
wrong.

Cheers,
Bruno
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] [proposal] global and per item data stashes

[Bruno Oliveira]

Hi Ronny,

As you have shared this before in chat, at first glance it sounds like a
good idea!

Some questions that we can probably elaborate on once we have something
more concrete to discuss:

1. You say "each stash  would be a context manager", but it is not clear to
me how this would work in practice, as most uses today that need to
decorate the object need to do it across multiple function calls (for
example, creating an object in `pytest_configure` and storing it in a
stash, only to retrieve the data later in another hook). Can you provide
examples to clarify this?

2. If we are to use the "stash" for fixtures, we need  a way to specify
stashes whose other lifetimes than function and session, like class, module
and package. Any idea how this would look like?

Other than that, where do you want to go from here? Keep the discussion
here in the mailing list, move it to the issue tracker, or somewhere else?

Cheers,
Bruno.


On Tue, Oct 15, 2019 at 10:03 AM Ronny Pfannschmidt 
wrote:

> Problem: for the storage of helper objects that either tackle certain
> global tracking details or that track information over the testprotocol
> lifecycle of test items, we use monkeypatchs and generally just munge
> around in either the pytest config object or item objects.
>
> I would like to propose a new API putting those details into consideration.
>
>
>
>   config.get_stash(owner, type=pytest.NamespaceStash) # valid over the
> pytest session lifetime
>   item.get_stash(owner, type=pytest.NamespaceStash) # valid across the
> run-test protocol cycle of item
>
> Each stash  would be a context manager and construction would get access
> to both item and config.
>
> This would for example enable to express the junit xml logger object and
> configuration as
>
> `config.get_stash(__name__, JunitXMlTracker)`
>
> Just as  it would allow other plugin to store node lifecycle related
> details within the node using a well known mechanism
>
> Incidentally this would also be a good fit for the fixture system and
> setup-state in general to store information.
>
> The basic assumption being that only the stashes of the items that are
> currently active are valid, and other stashes are torn down,
> then fixtures as well as the fixture request would nicely fit that storage
> mechanism, and would also generalize across the node tree from session down
> to individual items.
>
> (considering the layout, it might be sensible to even replace
> config.get_stash with something
> like session.get_stash)
>
> The idea is still rather fuzzy in my head and i would love to di either
> text based brainstorming on it, or a actual video call.
>
> -- Ronny
>
> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, 
> Eric Shander
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 4.6.6

[Bruno Oliveira]

pytest 4.6.6 has just been released to PyPI.

Backport of bug fixes for the last version to support 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/4.6-maintenance/changelog.html

Thanks to all who contributed to this release, among them:

* Anthony Sottile
* Bruno Oliveira
* Michael Goerz


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] transferring ownership of pytest-ordering

[Bruno Oliveira]

Good news Frank,

Once we have one or more active maintainers, we will be happy to transfer
the plugin to pytest-dev!

[]s

On Wed, Oct 9, 2019 at 11:13 AM Frank Tobia  wrote:

> Good point re: transfer ownership != maintenance handoff. I'll try to drum
> up some number of maintainers.
> At least one potential volunteer has reached out to me so far, so thanks
> for the tweet :)
>
> -Frank
>
> On Tue, Oct 8, 2019 at 6:41 PM Bruno Oliveira 
> wrote:
>
>> Hi Frank,
>>
>> Thanks for the interest in transferring pytest-ordering over to
>> pytest-dev!
>>
>> Keep in mind though that the intent of moving plugins over to the
>> pytest-dev organization is not to transfer maintenance responsibilities,
>> but a way for plugins to get more visibility and prevent "plugin
>> abandonment", where the sole maintainer is no longer responsive and the
>> plugin is effectively dead because nobody else has commit/publishing
>> rights.
>>
>> Having said that, before moving the plugin over to pytest-dev (which it
>> would be welcome otherwise!) I suggest to find some co-maintainers first,
>> so when the plugin gets transferred, it will have someone to fix the
>> eventual bug or merge a PR.
>>
>> People have had great success getting interested co-maintainers by
>> posting to mailing lists and Twitter, as well as asking if any of the
>> previous contributors would be interested in being co-maintainers; it might
>> be surprising how sometimes people step in.
>>
>> Let me know if you have any questions!
>>
>> Cheers,
>> Bruno
>>
>>
>>
>> On Tue, Oct 8, 2019 at 5:45 PM Frank Tobia  wrote:
>>
>>> Hi there,
>>>
>>> I wrote pytest-ordering but I haven't been doing a great job of
>>> maintaining it. I'd like to transfer ownership to the pytest-dev group if
>>> that's amenable. I think all the requirements for transferring are
>>> fulfilled but I'd appreciate calling out if I missed something (
>>> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
>>> ).
>>>
>>> Here's the repo: https://github.com/ftobia/pytest-ordering
>>>
>>> Thanks in advance.
>>>
>>> -Frank
>>> ___
>>> pytest-dev mailing list
>>> pytest-dev@python.org
>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>
>>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] transferring ownership of pytest-ordering

[Bruno Oliveira]

Hi Frank,

Thanks for the interest in transferring pytest-ordering over to pytest-dev!

Keep in mind though that the intent of moving plugins over to the
pytest-dev organization is not to transfer maintenance responsibilities,
but a way for plugins to get more visibility and prevent "plugin
abandonment", where the sole maintainer is no longer responsive and the
plugin is effectively dead because nobody else has commit/publishing
rights.

Having said that, before moving the plugin over to pytest-dev (which it
would be welcome otherwise!) I suggest to find some co-maintainers first,
so when the plugin gets transferred, it will have someone to fix the
eventual bug or merge a PR.

People have had great success getting interested co-maintainers by posting
to mailing lists and Twitter, as well as asking if any of the previous
contributors would be interested in being co-maintainers; it might be
surprising how sometimes people step in.

Let me know if you have any questions!

Cheers,
Bruno



On Tue, Oct 8, 2019 at 5:45 PM Frank Tobia  wrote:

> Hi there,
>
> I wrote pytest-ordering but I haven't been doing a great job of
> maintaining it. I'd like to transfer ownership to the pytest-dev group if
> that's amenable. I think all the requirements for transferring are
> fulfilled but I'd appreciate calling out if I missed something (
> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
> ).
>
> Here's the repo: https://github.com/ftobia/pytest-ordering
>
> Thanks in advance.
>
> -Frank
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.2.1

[Bruno Oliveira]

pytest 5.2.1 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
* Florian Bruhin
* Hynek Schlawack
* Kevin J. Foley
* tadashigaki


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.2 released

[Bruno Oliveira]

pytest-5.2.0
===

The pytest team is proud to announce the 5.2.0 release!

pytest is a mature Python testing tool with more than a 2000 tests
against itself, passing on many different interpreters and platforms.

This release contains a number of bugs fixes and improvements, so users are
encouraged
to take a look at the CHANGELOG:

https://docs.pytest.org/en/latest/changelog.html

For complete documentation, please visit:

https://docs.pytest.org/en/latest/

As usual, you can upgrade from pypi via:

pip install -U pytest

Thanks to all who contributed to this release, among them:

* Andrzej Klajnert
* Anthony Sottile
* Bruno Oliveira
* Daniel Hahler
* James Cooke
* Michael Goerz
* Ran Benita
* Tomáš Chvátal
* aklajnert


Happy testing,
The Pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.1.3

[Bruno Oliveira]

pytest 5.1.3 has just been released to PyPI.

This is a bug-fix release, being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The full changelog is available at
https://docs.pytest.org/en/latest/changelog.html.

Thanks to all who contributed to this release, among them:

* Anthony Sottile
* Bruno Oliveira
* Christian Neumüller
* Daniel Hahler
* Gene Wood
* Hugo


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Adding pytest-mpi to pytest-dev org on github

[Bruno Oliveira]

Hi James,

Thanks for the interest in moving the plugin to pytest-dev!

I don't think there are any problems other than the requirements described
here:

https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev


Let us know if you have any questions!

Cheers,

On Thu, Sep 19, 2019 at 10:23 AM James Tocknell  wrote:

> Hi pytest devs
>
> I've developed a small pytest plugin (
> https://github.com/aragilar/pytest-mpi) which assists with using MPI (
> https://en.wikipedia.org/wiki/Message_Passing_Interface) with pytest, and
> I'm looking for a github org to host it, would it be possible to have
> pytest-dev host it? Currently it is very under-documented, and needs
> tests/CI set up, as it's currently just a quick hack to support
> https://github.com/h5py/h5py/pull/1255, but I do plan on documenting it
> (which I need to do anyway so that other h5py contributors can use it), and
> adding proper tests, but let know if there's any major problems with this.
>
> Thanks
> James
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Strike for the climate on 20th (Friday)

[Bruno Oliveira]

Hi Brianna,

Sure, I've opened a PR for that:
https://github.com/pytest-dev/pytest/pull/5861

If nobody opposes this, I plan to merge this soon and create a pinned issue
stating that pytest developers won't be available tomorrow.

Cheers,

On Thu, Sep 19, 2019 at 3:03 AM Brianna Laugher 
wrote:

> I reckon go for it! Can we put a banner on the Github repo somehow?
>
> See you in the streets 
>
> Brianna
>
> On Wed, 18 Sep 2019 at 19:57, Bruno Oliveira  wrote:
>
>> Hi everyone,
>>
>> pytest, devpi and tox want to join the Digital Climate Strike which will
>> happen next Friday:
>>
>> https://digital.globalclimatestrike.net/
>>
>> The idea is to 1) not have the support team available on that day, as
>> well as perhaps 2) including a widget to the docs advertising the event,
>> such as this one:
>>
>> https://assets.digitalclimatestrike.net/demo.html?fullPage
>>
>>
>> (Note that it can be closed and still provide access to the docs).
>>
>> I think there will be almost no disruption, as sometimes issues sit
>> around for a day before getting an answer and the widget over the docs can
>> be dismissed with a single click.
>>
>> Opinions?
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Strike for the climate on 20th (Friday)

[Bruno Oliveira]

Hi everyone,

pytest, devpi and tox want to join the Digital Climate Strike which will
happen next Friday:

https://digital.globalclimatestrike.net/

The idea is to 1) not have the support team available on that day, as well
as perhaps 2) including a widget to the docs advertising the event, such as
this one:

https://assets.digitalclimatestrike.net/demo.html?fullPage

(Note that it can be closed and still provide access to the docs).

I think there will be almost no disruption, as sometimes issues sit around
for a day before getting an answer and the widget over the docs can be
dismissed with a single click.

Opinions?
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.1.2

[Bruno Oliveira]

pytest 5.1.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:

* Andrzej Klajnert
* Anthony Sottile
* Bruno Oliveira
* Christian Neumüller
* Robert Holt
* linchiwei123


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Fwd: pytest-mimesis transfer to pytest-dev

[Bruno Oliveira]

Got it, thanks! Should be all set, let me know if anything is amiss

On Sat, Aug 10, 2019 at 5:16 PM Никита Соболев 
wrote:

> Done, check your email.
>
> сб, 10 авг. 2019 г. в 22:05, Bruno Oliveira :
>
>> Nikita,
>>
>> The next step is to transfer the plugin ownership to one of the core
>> developers, feel free to transfer to me.
>>
>> Cheers
>>
>> On Sat, Aug 10, 2019 at 1:59 PM Arseniy Antonov 
>> wrote:
>>
>>> I like this plugin too.
>>>  Thank you for contributing.
>>> +1 .
>>>
>>> сб, 10 авг. 2019 г. в 14:41, Bruno Oliveira :
>>>
>>>> Great, thanks!
>>>>
>>>> Next step is to get approval from other core devs:
>>>>
>>>> > If no contributor strongly objects and two agree, the repository can
>>>> then be transferred to the pytest-dev organisation.
>>>>
>>>> You have my +1. :)
>>>>
>>>> Cheers,
>>>>
>>>> On Fri, Aug 9, 2019 at 7:37 PM Никита Соболев 
>>>> wrote:
>>>>
>>>>> Done! tox is introduced in this PR:
>>>>> https://github.com/mimesis-lab/pytest-mimesis/pull/73
>>>>>
>>>>> What's next?
>>>>>
>>>>> пт, 9 авг. 2019 г. в 15:32, Никита Соболев :
>>>>>
>>>>>> Ok, sounds fair!
>>>>>>
>>>>>> I will add tox.ini to the project and let you know.
>>>>>> I will then advertise the project on reddit / twitter / etc and
>>>>>> hopefully some users will be interested in helping out.
>>>>>> And since it is rather small - I can still do that myself.
>>>>>>
>>>>>> Thanks a lot!
>>>>>>
>>>>>> пт, 9 авг. 2019 г. в 15:27, Bruno Oliveira :
>>>>>>
>>>>>>> Hi Nikita,
>>>>>>>
>>>>>>> On Fri, Aug 9, 2019 at 6:14 AM Никита Соболев 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I would like to ask if you are interested in transferring
>>>>>>>> pytest-mimesis to https://github.com/pytest-dev ?
>>>>>>>>
>>>>>>>> I am asking because:
>>>>>>>> 1. I hope that it will increase the visibility of this plugin, we
>>>>>>>> have a lot of Mimesis users, but they rearly use this plugin
>>>>>>>> 2. I hope it will improve its maintenance, because currently I am
>>>>>>>> doing it on my own - and I don't have that much time to spend on it
>>>>>>>>
>>>>>>>
>>>>>>> Thanks for the interest in joining the pytest-dev organization!
>>>>>>>
>>>>>>> About 1, that's great, it is one of the main purposes of why the
>>>>>>> pytest-dev organization was created for.
>>>>>>> About 2, unfortunately in practice the maintenance will still fall
>>>>>>> under your shoulders. pytest-dev developers can eventually help with
>>>>>>> questions, but overall maintenance is still expected to be done by the
>>>>>>> original developer(s). If you are having trouble finding time to 
>>>>>>> maintain
>>>>>>> the plugin, I suggest to start looking for co-maintainers. A good way 
>>>>>>> to do
>>>>>>> that is to promote frequent contributors you trust to maintainers.
>>>>>>>
>>>>>>> Other than that, I see your repository has everything required
>>>>>>> except for a ``tox.ini`` file to facilitate contribution, which is one 
>>>>>>> of
>>>>>>> our requirements[1]. Do you think that could be added?
>>>>>>>
>>>>>>> So, having mentioned the point about maintenance and the tox.ini
>>>>>>> file, I think pytest-memesis would be a great addition to pytest-dev 
>>>>>>> IMHO.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Bruno.
>>>>>>>
>>>>>>> [1]:
>>>>>>> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
>>>>>>>
>>>>>>> If you are interested - what are the next steps?
>>>>>>>> If not - what recommendations do you have for us to improve the
>>>>>>>> project?
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Nikita Sobolev
>>>>>>>> https://github.com/sobolevn
>>>>>>>> ___
>>>>>>>> pytest-dev mailing list
>>>>>>>> pytest-dev@python.org
>>>>>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>>>>>
>>>>>>> ___
>>>> pytest-dev mailing list
>>>> pytest-dev@python.org
>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>
>>> --
>>> --
>>> Regards.
>>> Arseny Antonov
>>>
>>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Fwd: pytest-mimesis transfer to pytest-dev

[Bruno Oliveira]

Nikita,

The next step is to transfer the plugin ownership to one of the core
developers, feel free to transfer to me.

Cheers

On Sat, Aug 10, 2019 at 1:59 PM Arseniy Antonov 
wrote:

> I like this plugin too.
>  Thank you for contributing.
> +1 .
>
> сб, 10 авг. 2019 г. в 14:41, Bruno Oliveira :
>
>> Great, thanks!
>>
>> Next step is to get approval from other core devs:
>>
>> > If no contributor strongly objects and two agree, the repository can
>> then be transferred to the pytest-dev organisation.
>>
>> You have my +1. :)
>>
>> Cheers,
>>
>> On Fri, Aug 9, 2019 at 7:37 PM Никита Соболев 
>> wrote:
>>
>>> Done! tox is introduced in this PR:
>>> https://github.com/mimesis-lab/pytest-mimesis/pull/73
>>>
>>> What's next?
>>>
>>> пт, 9 авг. 2019 г. в 15:32, Никита Соболев :
>>>
>>>> Ok, sounds fair!
>>>>
>>>> I will add tox.ini to the project and let you know.
>>>> I will then advertise the project on reddit / twitter / etc and
>>>> hopefully some users will be interested in helping out.
>>>> And since it is rather small - I can still do that myself.
>>>>
>>>> Thanks a lot!
>>>>
>>>> пт, 9 авг. 2019 г. в 15:27, Bruno Oliveira :
>>>>
>>>>> Hi Nikita,
>>>>>
>>>>> On Fri, Aug 9, 2019 at 6:14 AM Никита Соболев 
>>>>> wrote:
>>>>>
>>>>>> I would like to ask if you are interested in transferring
>>>>>> pytest-mimesis to https://github.com/pytest-dev ?
>>>>>>
>>>>>> I am asking because:
>>>>>> 1. I hope that it will increase the visibility of this plugin, we
>>>>>> have a lot of Mimesis users, but they rearly use this plugin
>>>>>> 2. I hope it will improve its maintenance, because currently I am
>>>>>> doing it on my own - and I don't have that much time to spend on it
>>>>>>
>>>>>
>>>>> Thanks for the interest in joining the pytest-dev organization!
>>>>>
>>>>> About 1, that's great, it is one of the main purposes of why the
>>>>> pytest-dev organization was created for.
>>>>> About 2, unfortunately in practice the maintenance will still fall
>>>>> under your shoulders. pytest-dev developers can eventually help with
>>>>> questions, but overall maintenance is still expected to be done by the
>>>>> original developer(s). If you are having trouble finding time to maintain
>>>>> the plugin, I suggest to start looking for co-maintainers. A good way to 
>>>>> do
>>>>> that is to promote frequent contributors you trust to maintainers.
>>>>>
>>>>> Other than that, I see your repository has everything required except
>>>>> for a ``tox.ini`` file to facilitate contribution, which is one of our
>>>>> requirements[1]. Do you think that could be added?
>>>>>
>>>>> So, having mentioned the point about maintenance and the tox.ini file,
>>>>> I think pytest-memesis would be a great addition to pytest-dev IMHO.
>>>>>
>>>>> Cheers,
>>>>> Bruno.
>>>>>
>>>>> [1]:
>>>>> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
>>>>>
>>>>> If you are interested - what are the next steps?
>>>>>> If not - what recommendations do you have for us to improve the
>>>>>> project?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Best regards,
>>>>>> Nikita Sobolev
>>>>>> https://github.com/sobolevn
>>>>>> ___
>>>>>> pytest-dev mailing list
>>>>>> pytest-dev@python.org
>>>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>>>
>>>>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
> --
> --
> Regards.
> Arseny Antonov
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Fwd: pytest-mimesis transfer to pytest-dev

[Bruno Oliveira]

Great, thanks!

Next step is to get approval from other core devs:

> If no contributor strongly objects and two agree, the repository can then
be transferred to the pytest-dev organisation.

You have my +1. :)

Cheers,

On Fri, Aug 9, 2019 at 7:37 PM Никита Соболев  wrote:

> Done! tox is introduced in this PR:
> https://github.com/mimesis-lab/pytest-mimesis/pull/73
>
> What's next?
>
> пт, 9 авг. 2019 г. в 15:32, Никита Соболев :
>
>> Ok, sounds fair!
>>
>> I will add tox.ini to the project and let you know.
>> I will then advertise the project on reddit / twitter / etc and hopefully
>> some users will be interested in helping out.
>> And since it is rather small - I can still do that myself.
>>
>> Thanks a lot!
>>
>> пт, 9 авг. 2019 г. в 15:27, Bruno Oliveira :
>>
>>> Hi Nikita,
>>>
>>> On Fri, Aug 9, 2019 at 6:14 AM Никита Соболев 
>>> wrote:
>>>
>>>> I would like to ask if you are interested in transferring
>>>> pytest-mimesis to https://github.com/pytest-dev ?
>>>>
>>>> I am asking because:
>>>> 1. I hope that it will increase the visibility of this plugin, we have
>>>> a lot of Mimesis users, but they rearly use this plugin
>>>> 2. I hope it will improve its maintenance, because currently I am doing
>>>> it on my own - and I don't have that much time to spend on it
>>>>
>>>
>>> Thanks for the interest in joining the pytest-dev organization!
>>>
>>> About 1, that's great, it is one of the main purposes of why the
>>> pytest-dev organization was created for.
>>> About 2, unfortunately in practice the maintenance will still fall under
>>> your shoulders. pytest-dev developers can eventually help with questions,
>>> but overall maintenance is still expected to be done by the original
>>> developer(s). If you are having trouble finding time to maintain the
>>> plugin, I suggest to start looking for co-maintainers. A good way to do
>>> that is to promote frequent contributors you trust to maintainers.
>>>
>>> Other than that, I see your repository has everything required except
>>> for a ``tox.ini`` file to facilitate contribution, which is one of our
>>> requirements[1]. Do you think that could be added?
>>>
>>> So, having mentioned the point about maintenance and the tox.ini file, I
>>> think pytest-memesis would be a great addition to pytest-dev IMHO.
>>>
>>> Cheers,
>>> Bruno.
>>>
>>> [1]:
>>> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
>>>
>>> If you are interested - what are the next steps?
>>>> If not - what recommendations do you have for us to improve the project?
>>>>
>>>> Thanks!
>>>>
>>>> Best regards,
>>>> Nikita Sobolev
>>>> https://github.com/sobolevn
>>>> ___
>>>> pytest-dev mailing list
>>>> pytest-dev@python.org
>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>
>>>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Fwd: pytest-mimesis transfer to pytest-dev

[Bruno Oliveira]

Hi Nikita,

On Fri, Aug 9, 2019 at 6:14 AM Никита Соболев  wrote:

> I would like to ask if you are interested in transferring pytest-mimesis
> to https://github.com/pytest-dev ?
>
> I am asking because:
> 1. I hope that it will increase the visibility of this plugin, we have a
> lot of Mimesis users, but they rearly use this plugin
> 2. I hope it will improve its maintenance, because currently I am doing it
> on my own - and I don't have that much time to spend on it
>

Thanks for the interest in joining the pytest-dev organization!

About 1, that's great, it is one of the main purposes of why the pytest-dev
organization was created for.
About 2, unfortunately in practice the maintenance will still fall under
your shoulders. pytest-dev developers can eventually help with questions,
but overall maintenance is still expected to be done by the original
developer(s). If you are having trouble finding time to maintain the
plugin, I suggest to start looking for co-maintainers. A good way to do
that is to promote frequent contributors you trust to maintainers.

Other than that, I see your repository has everything required except for a
``tox.ini`` file to facilitate contribution, which is one of our
requirements[1]. Do you think that could be added?

So, having mentioned the point about maintenance and the tox.ini file, I
think pytest-memesis would be a great addition to pytest-dev IMHO.

Cheers,
Bruno.

[1]:
https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev

If you are interested - what are the next steps?
> If not - what recommendations do you have for us to improve the project?
>
> Thanks!
>
> Best regards,
> Nikita Sobolev
> https://github.com/sobolevn
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 4.6.5 released!

[Bruno Oliveira]

pytest 4.6.5 has just been released to PyPI.

The 4.6.X series is the last pytest series that still support Python 2.7
and 3.4, containing bug-fixes ported from the master branch.

For more information, see our 2.7 and 3.4 support plan:
https://docs.pytest.org/en/latest/py27-py34-deprecation.html

To upgrade:

  pip install --upgrade pytest

The full changelog is available at http://bit.ly/2Zvcxz0

Thanks to all who contributed to this release, among them:

* Anthony Sottile
* Bruno Oliveira
* Daniel Hahler
* Thomas Grainger


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] pytest 5.0.1

[Bruno Oliveira]

pytest 5.0.1 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:

* AmirElkess
* Andreu Vallbona Plazas
* Anthony Sottile
* Bruno Oliveira
* Florian Bruhin
* Michael Moore
* Niklas Meinzer
* Thomas Grainger


Happy testing,
The pytest Development Team
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev