Mailman 3 March 2021 - pytest-dev

Transfer of pyfakefs to pytest-dev?
by mrbean-bremen Sept. 30, 2022

Sept. 30, 2022

After the successful transfer of pytest-order (thank you for that smooth experience!), I have been thinking about the transfer of another library - pyfakefs - where I am a contributor. I have been discussing this with the package maintainer, John McGehee, who is also in favor for this, and decided to first ask here if that is feasible. pyfakefs (https://github.com/jmcgeheeiv/pyfakefs) is a library that mocks the file system. It has originally been developed by Mike Bland at Google, later transferred to GitHub (after the shutdown of Google Code in 2011), where John McGehee has forked it, added direct support for unittest and doctest, and has maintained it since then (with my help since a few years ago). Later a contributor added support for pytest via the fs fixture, with more support for pytest following eventually. Today the fs fixture is probably the main means to access pyfakefs, judging by the issues and the dependent repositories. So, while pyfakefs is not a pure pytest plugin, and it doesn't follow the naming convention pytest-xx, we thought that it would be a good idea to transfer it to pytest-dev, with the following goals: - ensure continued maintenance - increase compatibility with pytest and pytest-plugins - improve visibility of the package, especially for pytest developers - ideally, benefit from the larger community to get more code reviews and issue reports For reference see also https://github.com/jmcgeheeiv/pyfakefs/issues/590 What do you think? Thanks! -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

5 8

autospec for monkeypatch
by Brian Okken March 22, 2021

March 22, 2021

I think I want to get some extra help on this good question. - Brian - Brian Begin forwarded message: > From: Dimitri Blyumin via Fireside <contactform(a)fireside.fm> > Date: March 20, 2021 at 7:36:58 PM PDT > To: brian(a)pythontesting.net > Subject: [Test & Code : Python Testing] Listener Feedback from Dimitri Blyumin > Reply-To: dimitri.blyumin(a)gmail.com > > Name: Dimitri Blyumin > Email: dimitri.blyumin(a)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/)

3 3

Re: [pytest-dev] pytest documentation
by Daniele Procida March 14, 2021

March 14, 2021

Hello pytest team, now that I have been at this a few days, I wanted to check in to see how you feel how it's going. Does the burden of doing things this way seem excessive? Is there anything you would you like me to do differently, or are you happy for me continue like this? Thanks for merging all the PRs so swiftly. Daniele

3 2

Re: [pytest-dev] pytest documentation
by Daniele Procida March 14, 2021

March 14, 2021

[I actually sent this on Wednesday, but only just realised that I sent it to myself because of the reply-to - so it's a bit late] I've started now: <https://github.com/pytest-dev/pytest/pull/8430>. A few questions: would you like me to add something to the _changelog_towncrier_draft.rst or changelog.rst, even for these little changes? I don't want to pollute it with excessive noise. Secondly, would you like me to create an issue just to refer to this conversation, and for the commits to refer to? Finally, is there a way to run linting on the documentation only? Thanks, Daniele Daniele Procida wrote: >Bruno Oliveira wrote: > >>I definitely think it would be a good idea, but I'm interested to hear >>what the other maintainers think as well. > >I haven't heard any other replies - I would be glad to know what others >think, to be sure that this will be a good way forward and of benefit to >pytest (or not!). > >Thanks, > >Daniele > >_______________________________________________ >pytest-dev mailing list >pytest-dev(a)python.org >https://mail.python.org/mailman/listinfo/pytest-dev

2 1

Transfer of pytest-order to pytest-dev
by hansemrbean March 4, 2021

March 4, 2021

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

3 3

pytest-6.2.2
by Bruno Oliveira March 3, 2021

March 3, 2021

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

5 7