HTTP/2 200
date: Fri, 10 Oct 2025 06:26:38 GMT
content-type: text/html; charset=utf-8
django-composition: Swing From Paris
nel: {"report_to":"heroku-nel","response_headers":["Via"],"max_age":3600,"success_fraction":0.01,"failure_fraction":0.1}
referrer-policy: same-origin
report-to: {"group":"heroku-nel","endpoints":[{"url":"https://nel.heroku.com/reports?s=D6Utrb4qO6WPQ3Z5KsM%2BphxFjhQFnwcaOxNQtxnZPnE%3D\u0026sid=c46efe9b-d3d2-4a0c-8c76-bfafa16c5add\u0026ts=1760077598"}],"max_age":3600}
reporting-endpoints: heroku-nel="https://nel.heroku.com/reports?s=D6Utrb4qO6WPQ3Z5KsM%2BphxFjhQFnwcaOxNQtxnZPnE%3D&sid=c46efe9b-d3d2-4a0c-8c76-bfafa16c5add&ts=1760077598"
server: cloudflare
via: 1.1 heroku-router
x-content-type-options: nosniff
cf-cache-status: MISS
last-modified: Fri, 10 Oct 2025 06:26:38 GMT
vary: accept-encoding
content-encoding: gzip
cf-ray: 98c40c1dbe1e3c64-BOM
alt-svc: h3=":443"; ma=86400
Archive for Wednesday, 2nd September 2020
Wednesday, 2nd September 2020
I’ve identified a pattern for handling potentially-asynchronous callback functions in Python which I’m calling the “await me maybe” pattern. It works by letting you return a value, a callable function that returns a value OR an awaitable function that returns that value.
[... 787 words ]
