Whilst writing Speed Up Your Django Tests, I wanted to add a section about mocking the current time.
I knew of two libraries for such mocking, but I found it hard to pick one to recommend due to the trade-offs in each.
So I delayed adding that section and shaved a rather large yak by writing a third library.
transaction.on_commit() hook is useful for running tasks that rely on changes in the current database transaction.
The database connection enqueues callback functions passed to
on_commit, and executes the callbacks after the current transaction commits.
If the transaction is rolled back, the callbacks are discarded.
This means they act if-and-when the final version of the data is visible to other database connections.
My previously announced book “Speed Up Your Django Tests” is out now on Gumroad.
I’ve been writing since the 3rd March, so it’s quite a relief to have launched it.
It’s occasionally useful to be able to tell which Django
manage.py command is being run, in a code path that otherwise has no way of telling.
For example, in Speed Up Your Django Tests, I describe how to modify
manage.py to default use a test settings file when the
test command is run.
It’s been a year since I published How to Score A+ for Security Headers on Your Django Website, the blog post for my DjangoCon Europe 2019 talk.
It’s seen some updates as both Django and web security have evolved, for example Feature-Policy is now required for an A+, and Django 3.0 includes built-in support for Referrer-Policy.
Imagine you have some Django views using the same two decorators:
Python’s decimal module has concept of a “context.”
This defines the default precision of new
Decimals, how rounding works, and lots of other behaviour.
Maths gets complicated!
Django’s default settings file has always included a
I call it a “pseudo-setting” since it’s not read by Django itself.
But it’s useful for configuring path-based settings, it is mentioned in the documentation, and some third party packages use it.