This Week in Changelogs: flask, pytest, IPython, etc
pyenv 2.3.13, 2.3.14
Highlights from the changelog:
- added versions 3.10.10, 3.11.2, and 3.12.0a5;
- fixed versions 3.5.10 and 3.6.15 for macOS and modern 64-bit platforms.
This one made me laugh a bit:
That's how programming actually works!
TIL: head -n123
is a part of POSIX, head -123
is a shorthand that can be missing in some operating systems (pull request).
IPython 8.11.0
Highlights from the changelog:
%autoreload
supports meaningful parameters (%autoreload all
,%autoreload off
, etc), not only numbers (%autoreload 0
,%autoreload 2
, etc).
I like the log of the pull request, it illustrates the approach of implementing a feature step-by-step, one frame at a time:
Also, this fragment is quite interesting, print
and logger.info
need to be used carefully for logging and protected from being overwritten during hot-reload:
p = print
logger = logging.getLogger("autoreload")
l = logger.info
def pl(msg):
p(msg)
l(msg)
Everything you wanted to know about GitHub actions:
flask 2.2.3
Although the changelog is not that big, I like the thing about flask run --debug
.
Previously, it was flask --debug run
, and it was awkward. The fix itself is quite small, but there's a lot of changes in docs, and also a PyCharm screenshot was changed. Nice and pure!
pytest 7.2.1, 7.2.2
The changelogs contains mostly bug fixes. One of them is about pytest.approx()
causing ZeroDivisionError
on dicts.
Another one fixes type checkers behaviour for the following code, which I think should be illegal:
with pytest.raises(RuntimeError) if val else contextlib.nullcontext() as excinfo:
(Please, don't write the code like this.)
And they fixed a race condition when creating directories in parallel, using os.makedirs(..., exists_ok=True)
. Simple, but helpful.
whitenoise 6.4.0
The changelog mentions support for Django 4.2. It was good to know, by the way, that STATICFILES_STORAGE
is going to be changed to STORAGES
dict (pull request).
django-cors-headers 3.14.0
- added support for Django 4.2,
- switched from
urlparse
tourlsplit
.
The latter is the most interesting, urlsplit
is slightly faster. Also, it's cached, so sometimes you gain a huge performance.
The difference between these functions is that urlparse
includes parsing of the "parameters" section of a URL:
scheme://netloc/path;parameters?query#fragment
^ this
Since it's not widely used, in most cases it's safe to switch from urlparse
to urlsplit
.