florimondmanca

A list of ASGI-related Python packages I maintain:

• arel: Browser hot reload for ASGI apps.
• asgi-htmx: HTMX integration for ASGI applications.
• asgi-lifespan: ASGI lifespan utilities.
• asgi-sitemaps: Sitemap generation in ASGI apps.
• awesome-asgi: awesome ASGI resources
• msgpack-asgi: MessagePack support for ASGI apps.
• tartiflette-asgi: ASGI-based HTTP transport for the Tartiflette GraphQL engine.

tomchristie

class LifespanManager:
    def __init__(self, app):
        self.app = app
        self.startup_complete = asyncio.Event()
        self.shutdown_complete = asyncio.Event()
        self.messages = [{'type': 'lifespan.startup'}, {'type': 'lifespan.shutdown'}]

    async def __aenter__(self):
        self.task = asyncio.create_task(self.app(self.receive, self.send))
        await self.startup_complete.wait()

majackson

Django Migrations without Downtime

The following instructions describe a set of processes allowing you to run Django database migrations against a production database without having to bring the web service down.

Note that in the below instructions, migrations are all run manually at explicit points, and are not an automatic part of the deployment process.

Adding Fields or Tables

Adding a (nullable) field or a new table

1. Make the model or column addition in your code.

ygotthilf

ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key
# Don't add passphrase
openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub
cat jwtRS256.key
cat jwtRS256.key.pub

revolunet

Python VS ES6 syntax comparison

Python syntax here : 2.7 - online REPL

Javascript ES6 via Babel transpilation - online REPL

Imports

import math

zsup

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.