pytest fixtures nuts and bolts - revisited
https://pythontest.com/pytest-fixtures-nuts-bolts-revisited/
A series on pytest fixtures gets an update
- posts split into one concept each
- made sure all of the info was correct for modern versions of Python and pytest
- examples reran to make sure output is correct
#Python #pytest
New on blog: "EPYTEST_PLUGINS and other goodies now in #Gentoo"
"""
If you are following the gentoo-dev mailing list, you may have noticed that there’s been a fair number of patches sent for the #Python eclasses recently. Most of them have been centered on #pytest support. Long story short, I’ve came up with what I believed to be a reasonably good design, and decided it’s time to stop manually repeating all the good practices in every ebuild separately.
In this post, I am going to shortly summarize all the recently added options. As always, they are all also documented in the Gentoo Python Guide.
"""
https://blogs.gentoo.org/mgorny/2025/07/26/epytest_plugins-and-other-goodies-now-in-gentoo/
After a discussion about why omitting coverage for tests is not a good idea, I added a tip to our test tutorial: https://python-basics-tutorial.readthedocs.io/en/latest/test/pytest/coverage.html#coverage-tip
#Python #Testing #pytest #coverage
Say goodbye to the container testing headache! Learn how #pytest_container + test infra make testing apps inside #containers smooth and scalable (all in #Python) from this #oSC25 talk. #pytest #DevOps #openSUSE https://youtu.be/kU9NS1FpfY8?si=qyjoR5zfMWI7qpY3
Tired of reinventing the wheel for container testing? See how the #pytest_container plugin simplifies testing #containers with #Python in this #oSC25 talk! No more plumbing; just define, connect, #test and go. #pytest #DevOps #openSUSE https://youtu.be/kU9NS1FpfY8?si=qyjoR5zfMWI7qpY3
NumPy - SciPy - Pandas (2025-07-06, 6-day workshop)
PRE-REQ
You are expected to have programming experience with Python 3, Pytest, Poetry on GNU/Linux.
FOCUS
Features in the new releases
Key programming abstractions
Coding with Python Generics
DataFrame
Functional approach to writing code
Multi-core Performance benchmarking
Packaging considerations
ENVIRONMENT
GNU/Linux system
NumPy
SciPy
Pandas
Python 3.12+
Pytest
Poetry
Git
Event is free to attend but RSVP is required.
Absolutely safe for students and women to attend. Code of conduct applies.
RSVP Cairo (and Maghreb)
https://www.meetup.com/softwarehubcairo/
RSVP Ankara (and Turkmen)
https://www.meetup.com/softwarehub
RSVP Riyadh (and Mashreq)
https://www.meetup.com/softwarehubriyadh/
All members of the Ummah are cordially invited.
#NumPy
#SciPy
#Pandas
#Python
#Poetry
#Pytest
#DataScience
#DataEngineering
#SoftwareFreedom
#SoftwareFreedomProject
#GNU
#Linux
#Community
#Ummah
une bibliothèque pour mocker les ressources #AWS utilisées dans le code de production #Python que vous testez (S3, par exemple) : https://github.com/getmoto/moto
La page https://github.com/getmoto/moto/blob/master/docs/docs/getting_started.rst documente comment écrire les tests (#pytest, #unittest) et donne quelques conseils pour écrire du code de production plus facile à tester (en ce qui concerne les interactions avec boto3, le client vers les services AWS).
That won't work. It says so in the docs:
> pyfakefs will not work with Python libraries that use C libraries to access the file system.
Which is what numpy is doing.
@encthenet @rachelplusplus Dunno if you've considered this, or would consider it, but pytest has a plugin, pytest-fakefs (https://github.com/pytest-dev/pyfakefs), that implements an in-memory filesystem complete with file objects that you can use to test file handling code without having to put things on disk. IMO the plugin ecosystem for handling things like this is one of pytest's biggest advantages over unittest.
Or if you prefer, pytest also has built-in functionality that makes working with temporary files pretty easy.
Today's morning sessions are on Uyuni, #Aeon Desktop, #encryption on #Steam Decks, #Kalpa, branding, #pytest for #containers, #zypper speed and more.! https://streaming.media.ccc.de/osc25
Idle thought apropos of nothing specific:
The very same folks telling me BOTH that I MUST use pytest, and that Django MUST have its JSON API story built-in continues to be ironic.
I'd (probably) at least open with the thought that testing is easily as central to a language as JSON APIs are to a web framework.
I don't see a movement to merge pytest to the stdlib.
A tak poza tym, to wysłałem parę łatek, by ulepszyć funkcję epytest w #Gentoo.
Wymuszają krótkie podsumowania, załączają tworzenie plików junit .xml, żeby ułatwić maszynowe przetwarzanie wyników, i — co najważniejsze — dodają zmienną EPYTEST_PLUGINS, żeby podawać, które wtyczki mają być załadowane. Będziemy dążyć do tego, by całkiem odejść od domyślnego automatycznego ładowania wtyczek.
https://archives.gentoo.org/gentoo-dev/20250623184523.226345-1-mgorny@gentoo.org/T/#t
In other news, I've sent a few fun patches to improve epytest in #Gentoo.
This includes forcing short summaries, creating junit .xml for machine processing, and most importantly, EPYTEST_PLUGINS to handle specifying the plugins to load. The goal is to eventually move away from plugin autoloading by default.
https://archives.gentoo.org/gentoo-dev/20250623184523.226345-1-mgorny@gentoo.org/T/#t
Wspaniały dzisiejszy #Python: #Gentoo uruchamia testy w paczkach związanych z #ProtoBuf z pomocą #PyTest-forked, żeby obejść segfaulty podczas GC.
Oczywiście, oznacza to, że zwykłe programy też mogą łapać segfaulty przy wyjściu.
https://github.com/protocolbuffers/protobuf/issues/22067
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/protobuf/protobuf-6.31.1.ebuild?id=54e20d4bb0ec99ab868695a2980c4307d179cb10#n150
Nowadays in quality #Python: #Gentoo is running #ProtoBuf-related test suite via #PyTest-forked to workaround protobuf segfaulting during GC.
Of course, it implies random programs can segfault on exit too.
https://github.com/protocolbuffers/protobuf/issues/22067
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/protobuf/protobuf-6.31.1.ebuild?id=54e20d4bb0ec99ab868695a2980c4307d179cb10#n150
What am I doing instead of resting? Well, I'm playing with generating EPYTEST_DESELECT from `epytest --junit-xml=…`
https://github.com/gentoo/gentoo/pull/42606
https://github.com/projg2/gpyutils/blob/master/gpyutils/scripts/junit2deselect.py
@FrOSCon 
DevelopersIO 
