Django community: RSS
This page, updated regularly, aggregates Django links from the Django community.
-
How to add a .well-known URL to your Django site - Adam Johnson
-
How to add a .well-known URL to your Django site - Adam Johnson
-
Django - Visual Studio Marketplace
Extension for Visual Studio Code - Beautiful syntax and scoped snippets for perfectionists with deadlines -
javascript - Webpack: Generate index.html for use with Django - Stack Overflow
-
reactjs - How to set up Django and React project without having to deal with CORS? - Stack Overflow
-
Caching in Django With Redis – Real Python
-
About the structure — Documentation system documentation
-
Pascal Widdershoven | Using Webpack with Django: no plugins required!
-
django-lifecycle · PyPI
This project provides a @hook decorator as well as a base model and mixin to add lifecycle hooks to your Django models. Django's built-in approach to offering lifecycle hooks is Signals. However, my team often finds that Signals introduce unnecessary indirection and are at odds with Django's "fat models" approach. Django Lifecycle Hooks supports Python 3.5, 3.6, 3.7 and 3.8, Django 2.0.x, 2.1.x, 2.2.x and 3.0.x. In short, you can write model code like this: from django_lifecycle import LifecycleModel, hook, BEFORE_UPDATE, AFTER_UPDATE class Article(LifecycleModel): contents = models.TextField() updated_at = models.DateTimeField(null=True) status = models.ChoiceField(choices=['draft', 'published']) editor = models.ForeignKey(AuthUser) @hook(BEFORE_UPDATE, when='contents', has_changed=True) def on_content_change(self): self.updated_at = timezone.now() @hook(AFTER_UPDATE, when="status", was="draft", is_now="published") def on_publish(self): send_email(self.editor.email, "An article has published!") Instead of overriding save and __init__ in a clunky way that hurts readability: # same class and field declarations as above ... def __init__(self, *args, **kwargs): super().__init__(*args, **kwargs) self._orig_contents = self.contents self._orig_status = self.status def save(self, *args, **kwargs): if self.pk is not None and self.contents != self._orig_contents: self.updated_at = timezone.now() super().save(*args, **kwargs) if self.status != self._orig_status: send_email(self.editor.email, "An article has published!") -
ASGI from scratch - Let’s build an ASGI web framework
https://news.ycombinator.com/item?id=23644252 -
Ruby vs Python for web development | Imaginary Cloud
-
django-lifecycle · PyPI
-
Signals | Django documentation | Django
-
How to · Mottie/GitHub-userscripts Wiki
-
czue/celery-progress: Drop in, configurable, dependency-free progress bars for your Django/Celery applications.
Drop in, configurable, dependency-free progress bars for your Django/Celery applications. - czue/celery-progress -
Forms, ModelForms
ModelForms are very handy shortcuts for quickly building forms. In this lesson, in just a couple of minutes we build a form, write a view and template for it. -
Optimizing the Django Admin Paginator | Haki Benita
-
benmezger/pydebug: Decorators for debugging Python
This is a simple set of utilities which makes it easier to debug Python objects. Pydebug respects Django's config. It checks if the decorator is running within a Django project and DEBUG is set to True. If it's set to False, it simply returns the function. Installing You can install by cloning this repository and running pip install . within this directory, or you can install through Pypi, by running pip install python-pydebug. Requirements Although Pydebug uses Python's standard library, it tried to import Django to make sure you are not within a Django project. LibraryDefaults Cython- IPDBPDB Line-profiler- Line-profiler requires Cython to work, if IPDB is not found, it fallsback to Python's standard PBD library. NOTE: At the moment, it is not possible to add rkern/line_profiler as a requirements due to their install process. Check their README for installation instructions. -
Automatically Register All Models In Django Admin — Django Tips | Hacker Noon
-
Single Page Application + REST as an Abstraction: The Benefits of Decoupling Your Front & Back Ends | Caktus Group
Monolithic, consolidated applications are not bad. These are your Rails apps, your Django apps, etc. — the ones where your server sends back HTML and assets. You’ve faithfully followed the Model-View-Controller (MVC) pattern as best you can and your concerns are “separated.” This design principle is not passé. It just so happens that for a long time, it was your only option. For some time now, there has been an alternative. An alternative. Keep calm and don’t trash your Django app just yet. -
LoudSwarm - virtual conference interface for presenters to live-stream talks
-
The Framework For Perfectionists With Deadlines
-
How to share Django sessions across newly added subdomains - Stack Overflow
Change the session cookie name to make this work smoothly. -
Started writing Celery tips from my experience. Tutorial part coming soon.
-
django-postgres-fuzzycount/fuzzycount.py at master · stephenmcd/django-postgres-fuzzycount
