pytest-7.4.4
=======================================
pytest 7.4.4 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
* Ran Benita
* Zac Hatfield-Dodds
Happy testing,
The pytest Development Team
Hey!
[Cross-posted from GitHub discussions for visibility]
I'm happy to announce that in collaboration with OMICRON[1], I'm aiming
to organize another pytest development sprint in 2024!
Back in 2016, we had an amazing[2] development sprint in Freiburg,
Germany, with a successful crowdfunding[3] and 27 participants from five
continents meeting up for a week, to hack on pytest 3.0 and tox.
That sprint is where things were implemented which you still likely see
today: Renaming the `py.test` binary to `pytest`, the `--setup-only` and
`--setup-plan` flags, `-o` to override options - and countless other
features, bugfixes, and work on plugins.
In 2024, I'd like to repeat this, with the goal of having a nice mixture
of newcomers, plugin authors, people who have worked on pytest itself
before, and of course core developers.
We currently are looking at two possible dates:
- *June 17th to 23rd*, 2024
- *June 24th to 30th*, 2024
>From what things look like currently, @flub and @asottile would be in,
and @Zac-HD as well as @RonnyPfannschmidt answered "maybe".
Given some generous support by OMICRON (one big and two small meeting
rooms, reserved for the whole week), and given our OpenCollective
balance of ~$50k USD[4], we will be able to host a maximum of 35 people.
The details will still need to be discussed, but the idea is that we
(partially/fully) *pay for travel and accommodation for participants*
from pytest funds, and OMICRON will *offer free lunch* for all
participants.
Before we flesh out all the details, I'd like to open up to a bigger
audience: *If you might be interested in joining us*, please fill out
this survey[5] with your preferred date. Obviously nothing of this is
binding for now. I'm just trying to figure out how many people we'd be
likely need to budget for, before moving into the details.
# Venue
The sprint will be hosted by OMICRON in Klaus, Vorarlberg, Austria[6].
Klaus is inhabited by a whopping ~3000 people. Despite being somewhat in
the middle of nowhere, it's actually not too hard to reach:
- *~2-2.5h from Zurich Airport*, either:
- 1h 15min direct Eurocity to Bregenz, then 30min local train from
there
- 10min local train to Zurich main station, 1.5h direct Railjet to
Feldkirch, 10min local train from there
- *~1.25h by train from Friedrichshafen*: Train to Lindau, train to
Feldkirch, train to Klaus
- *~3h by train from Munich*: 2h direct Eurocity train to Bregenz,
30min local train to Klaus
- *~6.5h by train from Vienna*: just over 6h by direct train
(Railjet), and then another 10 minutes in a local train
# Activities
Obviously, we'll hack a lot on pytest! Exact topics will still need to
be discussed, but of course we can also sprint on whatever participants
find interesting, as long as it benefits pytest.
We'll make sure to spend time socializing as well obviously. No details
here either just yet, but we might have an evening barbecue at OMICRON's
venues, and go for a hike or two together while we're there!
Florian
[1] https://www.omicronenergy.com/en/
[2] https://blog.pytest.org/2016/pytest-development-sprint/
[3] https://www.indiegogo.com/projects/python-testing-sprint-mid-2016#/
[4] https://opencollective.com/pytest
[5] https://nuudel.digitalcourage.de/2tEsEpRcwMNcAXVO
[6] https://www.openstreetmap.org/#map=15/47.3075/9.6207
